GreenMachine

Shame the search function doesn't work better ... http://www.msfn.org/board/index.php?showto...ndpost&p=172039

Search my posts for LegacyDisable, and that should fix your problem.

How many are you using it for?

There are a few solutions in this thread: take your pick!

OK. Where do you think XPCREATE fits into the picture? Sounds like you need to read the MSFN unattended guide. I don't think there is a way to have WINNT.SIF in two different parts.

XP plus SP2 (slipstreamed) comes out to less then 700 MB. Either you did something wrong, or you added too many extra files. Post your LOGFILES.CAB if you think XPCREATE is in error. Welcome to MSFN!

Look OK to me, with a quick glance. The syntax looks fine anyway, I assume the PCI values are correct. My version looks like this: [SCSI] VIASRAID = "XPCREATE VIASRAID SATA/RAID Driver." [SourceDisksFiles] VIASRAID.SYS = 1,,,,,,4_,4,1,,,1,4 [SCSI.load] VIASRAID = VIASRAID.SYS,4 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3149 = "VIASRAID"I doubt that "viasraid.sys = 1,,,,,,3_,4,1" makes a difference, but I am not sure ...

Thanks again, Bilou! Looks like I'll need to revise the SATA stuff when I get back to work. I'll get back to you then. I was under the impression that 3_ or 4_ did not really mater, as well as the ending letters. I guess I should really break down, and get the Microsoft TEXTMODE stuff working.

Cool! Now you can put things back little at a time, until you break it, and you will know what causes the error. Glad we got you going.

Sorry, I haven't a clue. That is really not my area of "expertise" (I use the term loosely ... ) You would probably have better luck in the Unattended or Windows XP forum. In any event, Welcome to MSFN, Boopa!

Sorry, but I'm not sure ... I have used !VAR! when %VAR% would have worked, but my memory fails me as if to whether I have have problems using it when I should not. They way it works, basically, is you need ! when the value for the variable is not known when entering that section of code. A section of code is generally the part inside the parenthesis, as in a FOR loop or IF statement. If the value needs to change inside of this section, you need !. If it will only have one value for the entire section, % can be used. This is because the DOS style interpreter, COMMAND.COM, would interpret yhe whole section before running it. It would assign all the variables beforeexecuting the code. Now you can have the value assigned on the fly, e.g. inside the FOR loop, but need to "expand" the variable after the loop has started (delayed). Hope that made some sense ... I just got up, and I'm on my way out the door.

You mis-read the first post: Bugs that I said I'd be fixing. This is a bug that I haven't even implemented yet! Please, all, I was just looking for a little help with my memory. I think we have it covered, so I'm closing this one till I get back to my lab.

Eliminated the loose nut?Just kidding ... Sorry, I wanted to be the last post, so I know I don't need to come back to this thread!

Thanks for helping out, frankiboy_01. I cannot promise that this list will work in the future. Welcome to MSFN, YatYat!

That's a new one on me. I wonder why ... I'll have to check this out when I get back, but I've never seen the need before. Could it be due to a "flat" install?

I, too, am waiting for the Japenese SP2: I think it will simplify things for all of you. And I, too, am still of on "vacation", and don't feel a bit guilty of streching the european standard 5 weeks a bit! We'll get it all worked out ... soon.

For the moment there is not much need: you only need SP2, and possibly DotNetFX, Journal Viewer and HighMAT. We'll fix the list later (Tu sais bien: Aout = Vacances!) Welcome to MSFN!

So, it was a loose nut behind the wheel? No problem, no bother. It happens to the best of us. And since I forgot before ... Welcome to MSFN!

I suspect the reserverd characters in the echo statement Colon [:] and parens [()]

Thanks, urgan, I'll add it to my collection.

Allez, dit, I thought you were!

I, too, would have to suspect disk problems. Perhaps: Too fast of a burn, poor quality or incompatble media, dirty CD-ROM driver. Have you tested in VPC/VMWare, or verified with CDCHECK?

Or ... Son of a Batch?

Now that's a comment I like! (Gotta admit, I was a little worried when I just read the first line.)

OEMFWALL, a Microsoft Utility, is what you need. Google for info. You just need to run it (I do from SVCPACK.INF). Here is a link from Google: http://koti.mbnet.fi/lbl/oemfwall.exe