Okay, I found BCDW and finally have a multiboot CD. That program makes it easy. However, if you have used it, do you have any idea how I can get back to the CD menu from DOS?
Okay, so I guess I can use the 98 walkthrough for the DOS bootdisk, but its sooo confusing. For instance: http://flyakite.msfnhosting.com/98se.htm What the heck does that mean? I'm trying to use Win98, why is XP mentioned here?
This is all very confusing to me. All I need is an option to boot DOS or BartPE. http://flyakite.msfnhosting.com I read the site, but it doesn't have any listing for DOS. I tried reading two different Bart sites, and found both of them highly confusing. Should I just give up? Anyone wanna take me under their wing?
I guess I should have given more information. I need a script that can run from within Windows (specifically PE). The imaging process I've created relies on the Dell asset tag to name itself, and we're no longer using DOS bootdisks. The Dell Asset program only works in a DOS environment.
Will that execute all .cmds in the directory, and only once? EDIT: LOL, I guess I can't give this file name a .cmd, as it loops repeatedly then. What does the /c do? As it just errored out for me.
I ended up finding a script on the internets that involved unzipping it into the default user profile. I have no idea why, but it worked. Thanks for the help. <3
I know I've seen it here somewhere, but can't find it. Sadly, I suck at writing batch files, or I'd just do it myself. I'm hoping to use the batch file to install all my apps...
i guess that is essentially what I tried. I created a Default User profile and placed all the files in $OEM$\$1\Documents and Settings\Default User. The Windows install doesn't even appear to see it. I think it may be a permissions problem, but I don't really know...
I hate to be a total id*** here, but if you have a few minutes, would you mind translating some of the stuff in there? That's a pretty complex batch file for an id*** like me, so any and all English helps!
My sysprepped machines seem to choose an older driver (probably a default M$ driver), rather than using a newer driver that I'm pointing at in the OemPnPDriversPath in sysprep.inf How can I FORCE sysprep to use the updated driver? I'm pretty sure that all the drivers are WHLQ...
I've seen that before, but it seems like too much. All I need is to change the login name. Not sure I can justify a purchase, just to change the login name...