Upgrading from Windows XP to Windows 7 with USB media

I wasn’t in any hurry to switch to Windows 7, but when several places put the Windows 7 family pack on sale for $125 or thereabouts, I figured I’d better get it. The normal price on three upgrades is $100-$110 a pop. And you know how it goes. Once you get something, you really don’t want it to just sit on the shelf. Why let the software collect dust while I wait for 64-bit Firefox to arrive?

So I want to install it off USB. It’s easy, right? Well, it’s easy if you’re running Vista. But the instructions floating around for making bootable Windows 7 installation USB media don’t work if you’re running XP. At least they didn’t work from any of my XP machines. Read more

What to do when a Microsoft patch won’t install

Every once in a while, when you push patches for a living, you come across a time when a Microsoft patch won’t install. This is one of those times, and what I did to fix it.

So, Microsoft KB947742, an old .NET 1.1 fix, refused to install on one of the servers at work. When I ran the executable, all it did was pop up the window showing the Windows Installer switches or parameters. Searching Google turned up a number of people having the problem, but no solutions that worked, although reinstalling the .NET 1.1 Framework and the latest version of the Windows Installer are always good ideas when you run into weird problems. .NET 1.1 is extremely fragile anyway, and reinstalling it along with all applicable hotfixes has worked for me in the past to resolve weird issues, such as permissions issues showing up in the security log. Or .NET applications just suddenly not running anymore, even though they ran just fine yesterday.

I tried everything I could think of and finally stumbled on a solution. I have absolutely no idea why this works. First, I opened a command line, changed into the directory where I had stored the patch, and I ran the following command:

NDP1.1sp1-kb947742-x86.exe /extract .\947742

This extracts the update to a directory called 947742. Inside that directory, I found a single file, named NDP1.1sp1-kb947742-x86.msp. When I double-clicked on the file from Windows Explorer, it installed.

I’ve applied this patch on more than 100 servers and I recall only having the problem on one of them. And, oddly, all other .NET patches and for that matter all other recent Microsoft updates apply to this machine just fine.

I suppose the same fix could work on other Windows updates that supply only a window full of switches instead of installing, or other weird installation issues. It’s worth a shot if nothing else works and you can’t (or would rather not) open a support case with Microsoft.

This is a strange case. If you’re running WSUS or (better yet) Shavlik Netchk and a patch refuses to install, try logging in, downloading and running the offending patch manually and note any error messages. Maybe, just maybe, this fix will help you. Or better yet, maybe the patch will tell you what you need to fix, but don’t count on it.

When absurdity strikes, try extracting the patch and poking around inside, like I did in this case.

Rare DOS disk utilities

Mailbag:

RAM disk; Your book; Mobos; Monitors; Net folders

I’ve been doing a bunch of work in DOS the past few days, and I’ve found some useful disk tools. A lot of people use the shareware WinImage or GRDUW to create images of floppy disks. That’s with good reason, seeing as floppies are so unreliable–this way, you’ve got a backup on a hard drive or CD-ROM drive, and it’s so much more convenient when you need a particular disk to just grab a blank, make a fresh copy from an image, and go do your thing. But I found some DOS utilities, some recent and others oldies but goodies, that give you the functionality of these shareware utilities but with the advantage of being free, smaller, faster, and in most cases running on a wider variety of operating systems–all good things. So they don’t have a nice clicky mousey interface… I don’t like using a mouse anyway. Maybe you’re like me, or maybe you like powerful utilities and don’t mind giving up the mouse to be able to use them.

So here goes.

Creating disk images. My favorite is  Diskwarez DF — of course I like this utility, seeing as it bears my initials. DF is a short and sweet utility for creating and writing disk images compatible with Rawrite and the Unix dd utility. Runs under DOS and under Windows 9x and NT in a command window. There are dozens of DOS disk imaging utilities out there, but this one has the advantage of being compatible with a very common cross-platform standard. Check out the Diskwarez site, as it’s got tons of info on disk programming, as well as some other utilities like free disk editors. Despite the name, it’s not a pirate site–Diskwarez software is distributed under a free license somewhat similar to the GPL.

If you prefer self-extracting images, you can use the similarly named DOSDF to create them.

Bigger, faster, better floppies. The other feature of GRDUW is to format high-capacity floppy disks and floppies that give faster access than disks formatted with Windows Explorer or the DOS format utility. Enter FDFORMAT . You can do that and plenty of other cool things with this utility. You can gain more usable space on a 1.44-meg floppy without resorting to weird disk formats just by reserving fewer root directory entries. For example, FDFORMAT A: /D:16 gives you the maximum available space on a 1.44-meg floppy by reserving just 16 root directory entries (if you’re storing large files you don’t need more than 16 anyway, probably).

For extra speed, use Sector Sliding: FDFORMAT A: /X:2 /Y:3 speeds up the disk by 50-100 percent by arranging the tracks in a more optimal order. Supposedly you can gain even more speed by playing around with the gap length, but the author says disks are less reliable when you do this. If you’re more interested in speed than in reliability, add the /G:32 switch to the command listed above.

And by default, the boot sector on disks formatted by FDFORMAT automatically try to boot to the hard drive rather than giving you the dreaded “Non-system disk or disk error” message. Why couldn’t Microsoft think of that?

And of course you can also format high-capacity disks. Use the /F168 option to format a 1.68-MB floppy, and the /F172 option to format a 1.72-meg floppy. These switches can be combined with the others as well. Keep in mind that extra-capacity disks aren’t bootable.

FDFORMAT’s downside is it won’t run from inside Windows NT or Windows 9x. The best thing to do with it is to format a disk with it on a PC booted into DOS (DOS mode from Windows 9x’s boot menu is sufficient), then take that disk and use the aforementioned DF or DOSDF utilities to make an image of that disk, then when you need to format a new high-speed disk or a new disk that won’t give you errors when you leave it in the drive, use the image.

Formatting bad disks. And finally, for those dreaded Track 0 Bad errors that render a disk unusable, there’s FR , which uses workarounds to try to make the disk usable again. Typically I get rid of floppies with bad sectors pretty quickly, but if it’s an emergency, this program might bail you out. I used to get around Track 0 errors by formatting the disk in my Amiga–for some reason the disk always worked after that–but seeing as I usually don’t have my Amiga set up, this is an alternative.

And wouldn’t you know it, as soon as I wrote that I found a better way. SmartFormat also does Track 0 workarounds, uses the date and time to create unique disk serial numbers (instead of Microsoft’s license-plate method), provides a fast format that’s up to 60% faster than Microsoft’s method, and can optionally format 1.72-meg disks. SmartFormat runs within Windows, usually.

Mailbag:

RAM disk; Your book; Mobos; Monitors; Net folders

486s and Amigas and emulators, oh my

Recovering data from an old large hard drive out of a 486. Someone asked how. No problem.
What do is put both drives in a new(er) system, each on its own IDE channel as master, then autodetect the old drive with the BIOS’ autodetect drives feature. But, to be on the safe side, I don’t boot Windows. I don’t want anything to try to write to the old drive, because it may not work right the first time. Instead, hold down the control key while booting (if you have Win98; if you have Win95, start tapping the F8 key immediately after the BIOS boot screen comes up–if you get a keyboard error, hit F1 when it says, then resume your attack on the F8 key). Select Safe Mode Command Prompt Only from the menu. That will put you at a C prompt.

Your old(er) drive will be drive D. If you had other partitions on the drive, they’ll be lower in the alphabet as Dan said. We can tell you exactly how your drives will be mapped if you remember your partitions (or maybe you’re familiar with how drive letters get mapped already).

Now, I execute a DIR /S D: to see if it produced an error. If it doesn’t, try this to get your data (don’t type the comments in italics):

MD C:RECOVER create a destination for your data
SMARTDRV D- turn on disk caching to speed up –may not work but does no harm
XCOPY /S /E /V D:*.* C:RECOVER copy drive D in its entirety to the destination

With any luck, that’ll safely spirit all your data away to the new drive. This is more convoluted than using Windows Explorer, but it’s safer. (See why I disagree with the people who say command lines are evil and obsolete and we shouldn’t have them anymore?)

If that succeeds, power down, disconnect the old drive, boot Windows, and check to make sure your data is intact and not corrupt. If it fails, reboot, go into the BIOS, and change the translation scheme for the old drive (you have a choice between Normal, Large, and LBA–LBA is usually the default). Lather, rinse, and repeat.

The good news is, I’ve used this method numerous times to move data from old 486s to newer machines, so chances of success, though not guaranteed, are pretty high.

Maybe I don’t want that Amiga 1200 after all… I went ahead and downloaded UAE 0.8.8 Release 8, then downloaded Amiga In A Box, which gives me a nice, souped-up Amiga setup without me having to remember all the nuances of the OS and tweak them myself (including some nice PD and shareware stuff already installed, configured and running). I fed it my Kickstart ROM image and my Workbench disk, it copied the files it needed, and voila, I had a working AGA-compatible Amiga!

The package even includes TCP/IP support. While Web browsing on a 33 MHz machine is a bit slow, I found performance to be almost as good as Netscape 4.x on a 90 MHz Power Macintosh 7200.

I benchmarked it, and on my Celeron-400 with a pathetic Cirrus Logic video card (I really need to get a cheap TNT2) I still compared favorably to a 33 MHz Amiga 4000/030. (My old beloved Amiga 2000 had a 25 MHz 68030 in it.) Since the Amiga’s biggest bottlenecks were with the disk subsystem and the video–they were comparable in speed to the PCs of 1990 and 1991–even a slow-sounding 33 MHz machine runs pretty nicely. I could probably crank out a little extra speed with some tweaking, which of course I’ll do at some point.

Then again, maybe I’ve finally found a use for a 1.2-GHz Athlon… (Besides voice recognition.)

If you have an old Amiga laying around and want some nostalgia, go get this. There’s a ton of legal Amiga software at www.back2roots.org to experiment with. If you don’t have an Amiga but want to see what all the fuss is about, you can get Cloanto’s Amiga Forever package, which contains legal, licensed ROM and OS images. You’ve probably never heard of Cloanto, but they’re one of the largest remaining Amiga software publishers. They’re reputable.

Now I just need to get TransWrite, the great no-nonsense word processor that I bought when I first got my A2000, running under UAE.

Troubleshooting Windows keyboard shortcuts

Dave,
A friend of mine who uses Win98 has an irksome problem I don’t quite understand. Maybe you can shed some light on the matter.

Whenever he boots up, all the launch keyboard shortcuts defined in his desktop icon shortcuts are gone. He can manually select each one and redefine them (O for Outlook, W for Word and so on), but the next time he starts up (reboots), they’re all gone again.

These are stored in registry…?

/ Bo


Bo Leuf
Leuf fc3 Consultancy
http://www.leuf.com/

I’ve seen that problem in 95, 98, and NT4. It appears that if Windows Explorer is the currently active application, they’ll work, but if some other app has focus, keyboard shortcuts on desktop icons won’t work. The only workaround I’ve found for this is to store keyboard shortcuts in the start menu. Those seem to work all the time.

I don’t think they’re stored in the registry, but I’m not sure where they’re stored. Win3.x had keyboard shortcuts too. If I had to hazzard a guess, I’d say they’re probably stored in the shortcut files in 9x/NT and in the program group files in Win3.x.