Saved for later reference

online repository of stuff I had to google for hours to figure out – and random snippets of code

Preventing Java updates from installing Ask toolbar

Tags: , , , , , , ,

I found this tip on StackOverflow and wanted to mirror it here to go with my previous article on Java installs.

A Windows .reg file with

1
2
3
4
5
6
7
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft]
"SPONSORS"="DISABLE"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft]
"SPONSORS"="DISABLE"

will make the installer “just install”, no questions asked, and no toolbars sneaking in.

Some downloads: A premade .reg file, and the .reg file renamed to .txt (in case browsers/virus scanners prevent the previous download). Always verify the contents of .reg files before running them.

Share

“Please provide path to Windows media (x86 processor)” when installing printer

Tags: , , , , , , , , ,

When installing a new printer earlier, I first installed it in Windows Server 2008 R2 (which of course only exists in a x64 version), and tried to add the x86 (XP) driver since all the clients run XP.

After providing the “additional drivers”-wizard with the printer driver, it asked me to “Please provide path to Windows media (x86 processor)”, which was a bit difficult since I had no 32-bit media (I would have tried 2008 32bit or similar, if so).

Turns out, the solution is blindingly simple: Share the printer, and with an admin user (typically the same who installed the printer on the server), log on to an XP computer, and install the shared printer from there. It will ask you to provide the driver since the server has none. After installing, go into printer properties in XP, find Sharing, Additional drivers…, and check off “Windows XP/2000, x86”. The driver will be uploaded to the server.

Share

Fixing a RAID1 that suddenly becomes write protected (64 bit Windows)

Tags: , , , ,

Today, after rebooting from some Windows updates, my RAID1 disk suddenly was write protected – but a way to change it was nowhere to be found. After some digging, I found that others have reported the same problem.

Background

As far as I can tell, it seems to be a weakness in the 64-bit drivers for the on-board RAID on some motherboards that causes it. For the record, mine is a Gigabyte GA-EP45-UD3P, and I’m running Windows 7 RC (7100) 64bit, but it seems to be reported for all 64 bit versions of Windows.  Anyhow, the fix itself is simple, and seems to stick over reboots, and hopefully it’s permanently fixed.

Fixing the problem

To solve the problem, we need to open an elevated command prompt; in both Windows 7 and Vista, you do this easily by hitting the Windows button, typing “cmd”, right-clicking the “C:\ cmd” search result, and selecting “Run as administrator”. In Windows 7 you can also find Command Prompt in the Start menu and Ctrl-Shift-click it, to open it elevated.

(Disclaimer: The DISKPART tool can potentially remove/create partitions on your hard drive, so be 100% certain what you’re doing before you hit Enter)

In the elevated Command Prompt, type “diskpart” and press enter:

1
C:\> diskpart

On the diskpart prompt, list your volumes:

1
DISKPART> list volume

In my case, the volume on my RAID was volume 4, so I selected it:

1
DISKPART> select volume 4

…and then I marked it writeable like this:

1
DISKPART> attributes volume clear readonly

Here’s the entire segment in a screenshot (note that I did a couple of extra steps selecting the disk, this is apparently not necessary):

DISKPART commands for removing read-only

DISKPART commands for removing read-only

Share

© 2009 Saved for later reference. All Rights Reserved.

This blog is powered by Wordpress and Magatheme by Bryan Helmig.