"philo" wrote in message
>
> <snip>
>
>>> I tried the install several times with different XP Home Install
>>> Disks (I have several of them) each time formatting the hard drive
>>> first to make sure it was clean from previous tries. I think the
>>> error is coming from the floppy disks that were generated, but can
>>> not be positive. I don't think all the install CDs would have the
>>> same missing/corrupt file.
>>>
>>> Any help on this would be greatly appreciated.
>>
>> Just a guess but maybe the service pack level of the floppies and
>> CD do not match up.
I found the following article:
http://support.microsoft.com/kb/310994/
It lists 3 different downloads depending on which service pack level
you have for the Windows XP installation CD. That is why I figured
the OP downloaded the wrong version of these setup floppies.
>> Just get a bootable floppy that include IDE CD-ROM support (I'm
>> assuming you are using IDE optical drives). Go to www.bootdisk.com
>> to get one. Then use it to boot into DOS whereupon the CD driver
>> should've been installed which means you can navigate to the CD and
>> run the setup.exe from there.
>
> Close, but no cigar
> That advice is NOT quite correct.
>
> To install XP by using a win9x boot floppy...
> you need to load smartdrv
I didn't run the downloads to see what got put in the config.sys and
autoexec.bat files on the first bootup floppy. I did test the
boot98.exe (Windows 98 OEM bootable floppy image) from
www.bootdisk.com to see what it did. It creates a ramdrive (since
there is no guarantee that a hard drive is yet availble) because the
tools extracted from ebd.cab will exceed the capacity of a 1.4MB 3.5"
floppy. So I suppose that it figures that it has already taxed the
memory of which there might not be a lot and smartdrv is not critical
to a Windows install.
The part that is slowed down by not using smartdrv is the initial file
copy process that gets the system files and drivers in the partition
which gets used after the required reboot.
> (if you don't, then the installation will take 'forever' if it
> completes at all)
Yeah, might go slower but that doesn't prevent the install from
proceeding. From what I've heard, the initial file copy process might
take 3 times longer without smartdrv. That's not forever. Besides,
when the file copy process starts, why would I sit around twiddling my
thumbs waiting rather than go do something else? When I start the
coffee maker, I don't stand around waiting until it finishes it cycle.
I'll come back sometime later when I'm no longer busy with whatever I
went off to do during the big file copy.
> also...the command to start the install from dos is : winnt
> ("setup" would be used *only* from a gui based install)
Which program file do the setup floppies executed to start the Windows
XP install? I did find mention that 16-bit DOS requires running
winnt.exe to start the setup. I don't have the wallet anymore that
the install CDs came in or any other install instructions. From what
you mention, running setup.exe probably would immediately bitch that
it is a Win32 app and won't run in DOS. I'll have to remember that
winnt.exe gets used from a DOS shell. Thanks.
>> Stay informed about: Clean Install of XP Home