johnhc

rollcage, sounds like you mostly just need to do some research. Kurt_Aust has a great tutorial for x64 installs. AddOns will need to be made for x64 - see RyanVm forums for more information. AddOns are really easy to create, I made one for IE8, here. For individual programs, research. Plenty of sites offer DLs for x64, FileHippo is one. Have fun and come back with specific questions and problems. Enjoy, John.

watbox, hope things get resolved soon. What, Kels, I don't even have any fancy buttons! I have run several tests and I see no way for the nLite.cmd to get run more than once. It does look like nLite.inf gets run on every user log in - I really don't understand that. I do not understand what you mean by "nLite first-run commands." Here's my standard inculcation, but I do need to see your Last Session, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

Volatus, I am bumping this thread since you have not responded and edits do not bump. I also cannot send you a PM. Enjoy, John.

Megacherv, I know nothing about Mac computers or Boot Camp, but I see no reason an nLited CD would not install if a Windows XP SP2/3 CD will. Enjoy, John.

ahmad2080, the Last Session is in your source folder after running nLite unless you checked the Option to not save it there. If so there is a copy in the Windows\Program Files\nLite\Presets folder by date code. Please remember to attach it, not paste it. The 7B says you do not have the correct text mode drivers and it cannot find a drive to install Windows. Do a Google on BSOD error stop 7B and see what you find. I am really not sure what newsposter is talking about, but you have installed nothing, so of course you need to install. First you need to find the correct text mode SATA drivers. Please post the link to your MB driver DL site. Enjoy, John.

ahmad2080, Of course we want you to post the BSOD error code. Do you think we are clairvoyant here? Is it a 000007B, perhaps? If so, we are. Also, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

spearson, quick question, quick answer and quick solution.....what a deal! You are welcome. Have fun, John.

spearson, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. If you selected the Explorer Tweak "Explorer-Launch folder windows in a separate process", then this is probably your problem. You can test this by going to Folder Options under Control Panel and unchecking the option. Please report when you have a solution, so others can benefit. Enjoy, John.

meowing, the p only one is here,which I got to via Kurt_Aust's link on page 1 above. I also don't know what the s is about, so when you find out, please let us know. Enjoy, John.

cbuts05, first, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Also tell us what error you are getting and post a screen shot if possible. Look at SETUPP.INI in you CD and post what the Pid= value is and your CD label (something like ARPROxxx_ENU) . Please report when you have a solution, so others can benefit. Enjoy, John.

joa, check the RyanVM forum for Update Packs. Enjoy, John.

Jhorton, most of us here are English speakers. It would be preferable if you could post in English. I used Google Translate to translate and will try to find a question later. Enjoy, John.EDIT: OK, I understand. This is instructions in Español , not a question. Thanks, John.

jchoft, I also run VMware Server but have not used VMX. I suspect you cannot emulate SATA drives, but could be wrong. Your chances of finding an answer here, I suspect, are low. I would suggest you post in the VMware forums. Windows does not install drivers for hardware that is not present. You can place any knind of drivers into nLite and they will end up in the Windows\NLDRV folder but not installed unless Windows detects the HW. Good luck, John.EDIT: I should have pointed out that the text mode drivers are different. The last one loaded when Setup first starts, is the one that gets used. This needs to be the correct one for your hardware. John.

Volatus, I still don't know what is going on. Have you placed commands inside the nLite.cmd file itself or just used the RunOnce exit in Unattended to run a batch file? I use Kurt_Aust's method (see here), to run installs like you mentioned. The nLite.cmd file normally gets run out of RunOnce and can be seen in the Winnt.sif file. DOSNET.INF (or .IN_) is where nLite.cmd gets copied to the Windows folder, I think. As I stated before, when I log into my Administrator account, I see a flash of a command prompt and that is all (my CD was connected). This happens only the first login. I can go to the Windows\System32 folder and run nLite.cmd and it runs. If my CD is disconnected, then I get an error, but no flash of a command prompt. I see that the nLite.inf is in the Windows\INF folder. I have 4 RunOnce entries in my Registry. I may have more than XP since I am running x64. Attached is a screen shot of one. I still don't understand how your nLite.cmd is getting started. Please let me know if you have some ideas. Enjoy, John. EDIT: This is toward the bottom of nLite.inf: HKU,".DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce","_nltide_3",0x00020000,"rundll32 advpack.dll,LaunchINFSectionEx nLite.inf,C,,4,N"Perhaps this explains why this keeps getting run. EDIT2: I managed to get a copy on the command prompt that flashes across my screen on the first login of each of my users. Here is a screen shot. John.

Sotcr, I see no problem with your Last Session except you are running nLite to create an XP ISO under Windows 7. This will not work, as you have discovered. Try it under XP and be sure to start with a fresh copy of your source CD. Please let us know how you make out. Enjoy, John.

Sorry, ss4sgoku, I do not understand what you are asking here. Enjoy, John.

sbridge, no id***, just learning. Glad you are running and glad to help. Have fun, John.

gjb911169, see the folder structure graphic on the WPI web site. You need to read the instructions, but place your WPI folder in your source folder, before you run nLite, and also the $OEM$ folder. It has been a long time since I first did it, so, again I urge you to read the short tutorial on the WPI site and look at the folder structure. Have fun, John.

arpharazon, I have found USSF very useful. Sometimes you have to extract the installer and go again at a lower level. Kurt_Aust's Run1 has Firefox, VMware and Shockwave switches and many more. Windows does not install drivers for which there is no hardware. Since virtual systems have their own drivers for their virtual hardware, then yours are ignored. You will find them in C:\WINDOWS\NLDRV. The shutdown command at the bottom of Run1 is the restart command. If you open a command prompt and enter "shutdown /?'' without the quotes, you will see all the switches and functions of the command. If you are running VMware Server 2, then the audio driver is in VMware Tools. Enjoy, John.

fred6633, I agree with Sp0iLedBrAt, that SP3 will almost certainly be the last, but MS has not stopped support and continues to release updates. Since normal Windows install allows users to select components to install, I suspect if you install a hypothetically SP4 on your system with components removed, the SP that Windows Updates sends to your computer will know about your removed components and not try to restore or update them. Enjoy, John.

harryleg, I would at least ask for confirmation from the MB maker. I do not recognize the brand. If you know the manufacturer of the board, e-mail them and ask. It is to their advantage to allow you to run the OS of your choice. Some are still running W2K. Please let us know what you learn. Enjoy, John.

Volatus, this is very interesting and I will spend some time looking into it. I logged into my Administrator account (VM) and I saw a quick command prompt window. Something was trying to run - my CD was disconnected. The nLite.cmd file is still in my System32 folder. Puzzled right now. Enjoy, John.

tetrapro, I asked you to rename your cmdlines because nLite uses one to run nLite.inf, posted below. [COMMANDS] "rundll32 advpack.dll,LaunchINFSection nLite.inf,U" "rundll32 advpack.dll,LaunchINFSection RunWPI.inf,,1,N"I thought you might be copying your cmdlines over the top of nLite's after nLite runs. If so, you would kill nLite.inf. I put the line concerning WPI in the posted cmdlines and nLite added its part. I am not familiar with the OEM folder but I can see no reason this should be a problem. Basically, I think you can add almost any named folder to your ISO. They will just sit there unless you add code to use the data. You do need to be careful with $OEM$ and its contents, because Setup uses these - I use them to get files into the System32 and other folders. Enjoy, John.

g-force, my position is to take the poster's word for what they are doing. I know almost nothing about VLKs, so I avoid this specific issue. All this unless something is said to lead me to believe that the nLite license agreement is being violated. Then I point out the salient points of the agreement and ask the poster to read it and let us know if they are adhering to it. I have even posted the agreement (less than a page). If it is very obvious that the agreement is violated, then I refer to it and say we cannot help. Sometime I post a link to the MSFN Unattended Guide. These are tough questions that make me glad I am a technical person and not a legal one. I would be deathly afraid to have a legal mind issue an opinion on all of our use of these types of software systems. Hope this helps. Enjoy, John.

sbridge, again, I think nuhi was saying to place the CMPNENTS Folder into the same folder as the I386 folder - NOT into the I386 folder. Please try this and let us know how it works. Enjoy, John.