TXTSETUP.OEM and CD-ROM?
From: Gerry Hickman (gerry666uk_at_yahoo.co.uk)
Date: 03/01/04
- Next message: Adam Hutcheson: "Re: NOT XP, 2000 RIS with Intel Pro/100 VE"
- Previous message: Mike: "Convert fat32 to NTFS"
- Next in thread: Patrick J. LoPresti: "Re: TXTSETUP.OEM and CD-ROM?"
- Reply: Patrick J. LoPresti: "Re: TXTSETUP.OEM and CD-ROM?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 01 Mar 2004 20:43:53 +0000
Hi,
Trying to make an unattended CD-ROM with SPs for use with some
unformatted Dell servers; Perc 3/Di RAID controller.
I made the bootable CD with integrated service pack and winnt.sif in the
i386 folder. The winnt.sif contains sections for [MassStorageDrivers]
and [OEMBootFiles]. So far so good.
I followed Oli's advice from http://www.willowhayes.co.uk/ (Great site!)
and placed the $OEM$ folder in the root of the CD instead of under i386;
I have no idea WHY it has to go in the root, but I'm sure there's a good
reason.
I then created $OEM$\Textmode, and placed TXTSETUP.OEM in there together
with all the *.INF and *.SYS for the controller.
Obviously it does not work:)
The CD boots up, loads about 100 ancient SCSI drivers then says
"TXTSETUP.OEM caused an unexpected error (18) at line 1044 in
D:\NT\Private\NTOS\BOOT\Setup\OEMDISK.C"
LOL! There's only about 20 lines in my TXTSETUP.OEM (I guess it merged
it with TXTSETUP.SIF or something?) But where did this "D" drive come
from?? There's no logical drives yet! It's a new server with RAID sets
but that's all.
All we want to do is get the driver into memory so we can manually
choose a partition in textmode portion of setup and then let the rest
run automated.
About 100 possible issues spring to mind at this point:
1. The TXTSETUP.OEM I'm using was designed for a floppy drive, and
although I included the "tag" file in OEMBootFiles, it probably gets
confused.
2. Even if it could see the "tag" file, it probably would not be able to
find the driver files, because they're in $OEM$\TextMode (which resides
in an "unsupported" location at the root of the CD)!
3. Syntax for [disks] is different for NTFS and FAT, but what about
before you've got either!
So I'm assuming there must be a simple solution? Next step looks like
hacking TXTSETUP.SIF, horrible.
There seems very little into on the net about this kind of CD, apart
from a few people saying they couldn't get it working. It seems like a
really good thing to have? Network setups are nice for clients, but if
my main server is broken, it's not much use having a network
distribution point sitting on it! Or if the network was broken, or
over-run with viruses a CD could again be useful to get up and running
in a quick and safe way.
I read Patrick's TXTSETUP.OEM "story" at
http://www.mail-archive.com/unattended-info%40lists.sourceforge.net/msg00107.html
which was very helpful, but I think is more related to a "network"
installs. Same issues though.
-- Gerry Hickman (London UK)
- Next message: Adam Hutcheson: "Re: NOT XP, 2000 RIS with Intel Pro/100 VE"
- Previous message: Mike: "Convert fat32 to NTFS"
- Next in thread: Patrick J. LoPresti: "Re: TXTSETUP.OEM and CD-ROM?"
- Reply: Patrick J. LoPresti: "Re: TXTSETUP.OEM and CD-ROM?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
