Reply to Message

View discussion in a popup

Replying to:
jrichards
Contributor
Contributor

Did you check the /var/log/messages. It will show you

what files it is downloading from the textmode

directory. You should check if the mapping is working

properly before continuing. Be aware that the

installer is case sensitive, so rename the requested

files to whatever is in the log.

Also please try one or more of the following:

1. According to the KB article there should be

something in the .sif file like:

\[MassStorageDrivers]

"LSI Logic Fusion-MPT SAS Driver (Server 2003

32-bit)" = "OEM"

This will tell the installer to check the

$OEM$/TEXTMODE directory, check the SCSI section and

find the driver for the mentioned scsi device.

2. The line in the txtsetup.oem should read:

d1 = "LSI Logic Fusion-MPT SAS Storport Driver",

w23dsk1, \

(replace the backslash before w23dsk1 with a space

and remove the space at the end of the line just to

make sure...)

OK, fixing my MassStorageDrivers entry (and figuring out that /etc/tftpd.map had a typo in it) i got windows to boot enough to see the two SAS drives, and start checking for previous installations of windows.

then i see it hit txtsetup.oem file, and it immediately returns the error:

\-------

the manufacturer provided file that setup is trying to use is corrupted or invalid:

Line 1 contains a syntax error.

setup cannot continue.....blah blah.....

\----


bear in mind i'm a total noob with windows network installs so i'm not totally sure if that error points at txtsetup.oem, or something else but so far google searching the issue points me to the d1 entry in txtsetup.oem being wrong?

Reply
0 Kudos