(no subject)
Nov. 8th, 2003 01:18 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jenkIn the continuing saga of Jesse's computer, he's got his old HD with new everything else. He arrived at ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
runnerwolf's midway through ceremony, explaining that a) he boots off the setup CD, it "loads" files, then hangs; and b) if he booted off a floppy made on my machine, there is no C drive - and can't run fdisk.
The good: Jesse's HD may be alright. Turns out the boot floppy XP creates is DOS (why----?) which does not grok NTFS. So not being able to see the C drive after booting from that floppy tells us nothing about whether the drive is okay or not.
The bad: And, of course, the boot floppy does not run the commandline diskpart utility.
The good: I had thought Jesse had booted off the XP cd, skipped the "recovery console" (aka: commandline, where one can go check out the C drive) option to install XP, and that XP setup had died partway through. Turns out that he boots off the XP cd and setup dies just *before* getting the menu to go into commandline mode or run setup.
The bad: Setup dies before getting the option to go into commandline mode, which would let us take a look at his C drive and see if the data is there or just random bits & bytes.
The good: Looks like we're getting him a new HD so he can do a clean install. There's a good shot that we'll be able to make his existing drive a second drive, so he'll have all his data available plus more disk space.
The bad: "A good shot" is not the same as "done".
runnerwolf's midway through ceremony, explaining that a) he boots off the setup CD, it "loads" files, then hangs; and b) if he booted off a floppy made on my machine, there is no C drive - and can't run fdisk. The good: Jesse's HD may be alright. Turns out the boot floppy XP creates is DOS (why----?) which does not grok NTFS. So not being able to see the C drive after booting from that floppy tells us nothing about whether the drive is okay or not.
The bad: And, of course, the boot floppy does not run the commandline diskpart utility.
The good: I had thought Jesse had booted off the XP cd, skipped the "recovery console" (aka: commandline, where one can go check out the C drive) option to install XP, and that XP setup had died partway through. Turns out that he boots off the XP cd and setup dies just *before* getting the menu to go into commandline mode or run setup.
The bad: Setup dies before getting the option to go into commandline mode, which would let us take a look at his C drive and see if the data is there or just random bits & bytes.
The good: Looks like we're getting him a new HD so he can do a clean install. There's a good shot that we'll be able to make his existing drive a second drive, so he'll have all his data available plus more disk space.
The bad: "A good shot" is not the same as "done".
