ESM69 Posted June 27, 2009 Author Share Posted June 27, 2009 well, i don't have a lastsession.ini file in my current sourcei'm using nLite just to create the .iso, nothing elsei create unattended.txt through the SP2 Deploy Tools, rename to WINNT.SIF and move it to my i386 folderi'm gonna take a step back from the ledge and try creating my image with CDImage and take nLite out of the equation altogetheri'll update in a bitE-- Link to comment Share on other sites More sharing options...
Guest Posted June 27, 2009 Share Posted June 27, 2009 Ah, I missed you saying that before. I believe nlite will reorganize the inf files even if its just making the iso. That shouldn't be a problem though. Also, disregard what I said earlier....you can run nlite multiple times against the same source if that's all you're doing with it.Something must be borked with your winnt.sif then. Here's mine. WINNT.SIF Maybe it will help. Link to comment Share on other sites More sharing options...
ESM69 Posted June 27, 2009 Author Share Posted June 27, 2009 Ah, I missed you saying that before. I believe nlite will reorganize the inf files even if its just making the iso. That shouldn't be a problem though. Also, disregard what I said earlier....you can run nlite multiple times against the same source if that's all you're doing with it.Something must be borked with your winnt.sif then. Here's mine. WINNT.SIF Maybe it will help.ok, a couple small differences between my WINNT.sif and yoursMsDosInitiated:mine: ="0"yours: =0OemSkipEula:mine: =Yesyours: ="Yes"to double quote or not to double quote, that is the questionmaybe?hard to tell when double quotes are needed or not...my quotes, with and/or without, were all setup via the SP2 Deploy Toolshave to go to work now so i'll try to remember to play with this tonight/tomorrow and see what i get...i can kind of see the MsDosInitiated value being a difference makerE-- Link to comment Share on other sites More sharing options...
ESM69 Posted June 30, 2009 Author Share Posted June 30, 2009 haven't had time to test this yetRL sucks a$$ sometimesas soon as i get a couple hours to go through things and make sure my source files are what they should be and then test i willi'll post my results as soon as i canE-- Link to comment Share on other sites More sharing options...
Guest Posted June 30, 2009 Share Posted June 30, 2009 (edited) I was going to suggest that. If your winnt.sif is ok what else could it be. About the quotation marks. It's a mystery to me. I know in the past having them or not having them in certain places will cause a failure.A while back, I went about trying to figure out the minimun needed in WINNT.SIF to only insert the key. In XP SP3 this is what I found...Minimun needed in WINNT.SIF to insert key - XP (SP3 only)[Data]MsDosInitiated=0UnattendedInstall="Yes"[Unattended]UnattendMode=ProvideDefault[UserData]ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"ProductKey and UnattendedInstall can be with or without quotes. On SP2 having quotes around product key caused a failure. On SP1 it's the opposite. See here: http://www.msfn.org/board/index.php?showto...st&p=194436If I get bored one day, I'll strip all the quotes and test in a VM then add quotes to everything and retest. I'm hoping MS did the right thing and made it so SP3 doesn't care one way or the other. Edited June 30, 2009 by -X- Link to comment Share on other sites More sharing options...
ESM69 Posted July 1, 2009 Author Share Posted July 1, 2009 well, something is teh suck and i don't know whatdidn't work againwell, i'm tired of playing with this atm...i found the RunOnceEx program that basically creates the RunOnceEx.cmd file, but also has a bit of code to identify your cd-rom drive; and, then installs from the cd and not the <install> directory, etci had that working the other day; so, i'm gonna go with that just to get the system back up and runninghowever, it's really pi$$ing me off that i can't get this to work...i'm sure, since i have nothing better to do, that i'll fiddle with this and try to figure out WTF is going ononce, errrrr, if i get it figured out i'll definitely post my findings/info/etcthanks, -X- for your time and suggestionstake careE-- Link to comment Share on other sites More sharing options...
pm* Posted July 1, 2009 Share Posted July 1, 2009 When You Enabled OEM Preinstall it will apperars the folder $OEM$ on your installationTo make $OEM$ Folder Make Sure That u have enabled the OEM Preinstall Link to comment Share on other sites More sharing options...
beats Posted July 1, 2009 Share Posted July 1, 2009 (edited) Also try adding: OemFilesPath="..\$OEM$" in the [unattended] section. Edited July 1, 2009 by beats Link to comment Share on other sites More sharing options...
ESM69 Posted July 3, 2009 Author Share Posted July 3, 2009 this is weirdi went ahead and burned my install disc with the RunOnceEx.cmd that searches for and installs from the CDRomhowever, during the file copy stage i saw it copy the $OEM$ files that i wasn't seeing when i was testing with VMWaresure enough, the files and folders are on my c:\not sure why it worked this time and not when i was testing with VMWaremeh...feel like a tool for wasting your time, -X-E-- Link to comment Share on other sites More sharing options...
mikerz Posted July 4, 2009 Share Posted July 4, 2009 i added a 'pause' to my RunOnceEx.cmd file and found that cmdow is not being copied to \windows\system32...i just did a search of my "c:\" (on VM pc) and cmdow is definitely nowhere to be found...i'm not sure if cmdow not getting copied over is my main problem or something elseanyhow, what i've been doing is to use that XP_SP3_Base to make a .iso file and tested that it loaded in VM Machine and that i hade that "base install" then, i unzipped that .iso file to XP_SP3_062509 so i could mess around with my "source" data and if/when i screwed things up, i could just go back to my XP_SP3_Base main source and start againwhen i did this in the past, i remember being able to update my current source and just roll on...i'm not sure if i used nLite or what back then...i don't recall having to delete anything, etcalso, here's the $OEM$ folder structure you asked about:$OEM$ folder:$OEM$\$$\System32 folder:i really appreciate your feedback, -X-E--Just because the I386 folder is not in the root directory then try placing the $OEM$ directory inside the I386 directory... Link to comment Share on other sites More sharing options...
richiboy Posted July 7, 2009 Share Posted July 7, 2009 (edited) This seems to be a VMWare issue. I experience the same problem, but yet, when i run my UA in VirtualBox all is good! Don't ask me why, but it must be a settings or some sort of misconfiguration within VMWare? I Spent stressful hours trying to sort this out, $OEM$ not getting copied over etc... But when reading these forums I cam across a thread that had an similar issue. Within that thread some one said that he uses VirtualBox and advised him to try that out - So i thought ill try it too. Lo and behold, it worked! $OEM$ got copied over! But my only problem is with VirtualBox is that I can't get the "install from CD" with RunOnceEX to work when not using the /INSTALL folder etc... LOL NVM... I love the stress :SAnyways, hope this might help... Would be nice if you let me know or some one else could clarrify this with the VMW/VB ? or have had a similar issue? Edited July 7, 2009 by richiboy Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now