According to my knowledge the $OEM$ directory must not be created inside the i386 directory, but along side it.

ie.

CDROM:\$OEM$\$1 ... etc.

CDROM:\i386\

Not

CDROM:\i386\$OEM$

but i could be wrong

that's what the guide said idd, but i tried it and it didn't work untill i placed $OEM$ inside my i386 folder

*shrugs*

Strange

http://support.microsoft.com/support/kb/ar...s/q254/0/78.asp

Create a $oem$\$1\Drivers folder in the I386 folder. ...

if microsoft says it, it's true !!!!!!

lol

If Microsoft says it, then it must be a load of bollocks

http://support.microsoft.com/support/kb/ar...s/q254/0/78.asp

Create a $oem$\$1\Drivers folder in the I386 folder. ...

if microsoft says it, it's true !!!!!!

lol

um thats old and only is supposed to work wiht windows 2000.

Hi People...

Thanks all... AaronXP thanks the problem was OemPreinstall

changed auf Yes and it run without problems.....

have a other problem, bevor the GuiRunOnce batch start. Ask me the windows install username ... i see same fields and can creat users. What is this for a problem ?

thanks a lot

Negerle

http://support.microsoft.com/support/kb/ar...s/q254/0/78.asp

Create a $oem$\$1\Drivers folder in the I386 folder. ...

if microsoft says it, it's true !!!!!!

lol

um thats old and only is supposed to work wiht windows 2000.

i can only say that i used it with win2003 and then it suddenly worked

of course with the OemPreInstall on Yes, but even with OemPreInstall on yes it didn't work when $OEM$ was not under my i386 dir

well this guide was not for 2000 or 2003 really. It was intended for xp. This would also seem to be very telling. In that xp I'm more sure than ever now is built on top of win9x and 2003 is still diverging from the 2000 code base. Very interesting indeed. This way microsoft can kep the home user os buggy as all get out without affecting their server os as much.