johnhc

galocza, I am suspicious of using an x86 Last Session.ini on an x64 system. I use x64 and know nLite offers different options than it does to x86. I am not sure what to suggest yet, but I would like to see the Last Session for the 9 above. I would also like to see a Windows Explorer screen shot of the AMD64\NLDRV\001 folder in your source folder after running nLite. Enjoy, John. EDIT: I think Kurt_Aust is on to something along with using an x86 Last Session on an x64 system. I suggest you try starting from scratch (including a fresh copy of your CD files/folders) with a printed copy of your original Last Session. Go through all the Tasks/Options and select all the ones presented on your x64 system. Integrate only the SI driver - the unmodified one with only moving the txtsetup.oem folder into the ext64 folder. Please let us know if you fail to find any items in your original Last Session on your x64 system and please let us know the results.

galocza, we know that using OEM Preinstall will cause inclusion of text mode drivers via F6 to fail when using nLite. Please see the Help (? in a circle) next to the OEM Preinstall option in the Unattended section - General tab. I still need you to answer the questions in my last reply. Have fun, John.

pila2, please translate the error message into English and, 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.

andreyvul, please attach your latest Last Session.ini. Enjoy, John.

galocza, I am not sure what you are saying. What happens when, using the DLed (unmodified original SI) driver, you place the txtsetup.oem into the ext64 folder and point nLite to the .inf in the ext64 folder? I obviously do not understand why you are modifying files. Please give me some more detail. Enjoy, John.

CutTheGrass, I don't know what OS you will be nLiteing, but if it is XP x64, then you need VMware Server or VirtualBox because only they support x64. They all support 32 bit XP. VMware Server is by far the largest (DL probably greater than 500 MB), so please do some searching and consider VirtualPC or VirtyalBox. I use neither (I'm using x64), so I cannot recommend. Enjoy, John.

CutTheGrass, great title, thanks! Your statement is correct. NLite is fun to play with. Just try some things and see what happens. I suggest you consider a virtual system (VMware Server, VirtualPC and VirtualBox are all free) for testing and playing. Here is my standard inculcation if you have problems: 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.

andreyvul, remember we warned you before about running nLite under Vista to create an XP ISO. Can you run nLite under XP? What does this mean? Are you getting error messages during install? You should get no errors running nLite or during install. Enjoy, John.

MrJinje, I cannot answer your question but I used to use Firefox and participated in the forum. A number of people wanted to remove IE and the experts warned them not to do it! I also caution people not to remove IE since it is so intertwined with Windows. I kinda think DLing Firefox from another machine and installing it on the crippled one is another possible solution - good suggestion. Enjoy, John.

CutTheGrass, please Edit (full edit) and change your title to something more germane. The Forum Rules (see link at top) look askance on these types of titles. Now, I check nothing in the Compatibility list. This list just prevents you from removing components that are needed in those areas. At the bottom of the Component Removal section is a drop list labeled Presets. There are a couple of predefined ones there. It has been a long time, but I think I started with the safe one and then removed a few more things I knew I would never need. A caution; once removed, components are very difficult to reinstall. You have good reason to be careful. Enjoy, John.

rankena, here is something to try - don't know if it will work. Insert your ORIGINAL CD and it should auto start and display the screen I have posted here. Select Install Optional Windows components. Find Internet Explorer and install it. Since this may not work, I suggest that you create a System Restore point before you start. I am curious how you are communicating with us here if nothing works? If you have a running computer (apparently you do), you could DL IE8 to a USB stick or CD and install it on your crippled machine. Good luck and please let us know how you make out. Enjoy, John.

Thanks 5eraph and Fernando 1. I could see that the versions were the same, but I was confused by the fact that the normal driver of the 9.5.2 set (version 3.0.4.70 dated June 1, 2009), was not the same file (different hash) as the text mode. I think LSI-3Ware released a complete code set even though the drivers did not change (at least 64 bit ones - did not look at 32 bit). The software and the controller firmware did change. In fact, the latest firmware gave me a little performance boost. I think I now understand about DriverPacks. I was under an erroneous assumption that they were similar to Update Packs and AddOns. I am not interested in the real DriverPacks, and it looks like there are none for XP x64 anyway. Thanks to both, John.

Fernando 1, what prompted all these questions is that LSI-3Ware released code set 9.5.3 and I was looking at the drivers. The text mode and normal drivers are the same and the same as the 9.5.2 text mode driver. The only differences I can find, in the 9.5.2 code set, and identify with a comp command and a hex editor is the Digital Signatures have a different time stamp. The driver I find in my drivers folder is the text mode driver. I am thinking I do not need what I call Normal drivers for my controller. Any comments? Thanks, John.

Fernando 1, ever once in a while I realize how little I know. I asked you before about a running Windows using the text mode driver - you said yes. For my 3Ware controller, I have always included both a normal and text mode driver. Please see attach screen shots. Both pairs of .inf files are identical (same hash), the .sys files are exactly the same length but not identical (different hash) and the .cat files are not the same (different length). The pairs of file names are all the same. They are both in the NLDRV folder in two separate folders. So, which driver does Windows use when running (not installing)? Do I really need to include both? What is the difference in the two .sys files? Why are the .cat files different? Is there not something called a Driver Pack that can be included in nLite in a manner similar to Update Packs and AddOns? Thanks, John.

Fernando 1, because you called them "driverpacks ". I have never used a Driver Pack. Where do they go? I knew you deleted the USB boot devices - otherwise LSI-3Ware files. Thanks, John.

Fernando 1, you refer to these two files as "driverpacks ". I DLed the x64 one and extracted it. It looks like it is simply the driver files from LSI-3Ware compressed with 7-Zip. Can this be placed into the hot fix section of nLite? Is this all there is to driver packs for nLite? Thanks, John.

benbenno, see my reply to your .NET question. Enjoy, John.

benbenno, as I pointed to before, please see the Kurt_Aust tutorial. That is the method I use to install .NET and its updates. Enjoy, John.

5eraph, I suspect you well know that I almost always ask for the Last Session.ini and I want to encourage all posters to attach it as soon as it is available. It tells us many important details about what the poster is doing without asking 64 questions. I ask that you please don't discourage posters from attaching their Last Session.ini. benbenno, I would still like to see you attach your Last Session.ini. Enjoy, John.

benbenno, no need for an instruction manual. This has been addressed many times before and lots of information can be found via a search of this forum. Enjoy, John. EDIT: You do not add .cab or .exe files to nLite Hot Fix section. Some AddOns are .cab files and can be added into the Hot Fix section.

benbenno, I use XP x64 and an IE8 slipstream AddOn that has no updates. I then add what updates I can via the Hot Fix section and some that will not integrate I use the Kurt_Aust technique to add them via the RunOnce exit in the Unattended task. I also use his method to add DirectX9 (to answer your other post). Enjoy, John

benbenno, we need to see your Last Session.ini - please attach (not paste) it. I do no edit the winnt.sif file and you should not need to do so. I use Fully Automated under Unattended Mode of the General tab and I also define an account with administrator privileges with a password and auto log it. I also provide a PW for the Administrator account. I do not skip OOBE. All of this is why we need to see your Last Session. The only stop I get during install is when Setup asked you to define a partition to install Windows. Then completely unattended - i.e., no input required. Enjoy, John.

4875720, been there, done that. Please see here. I, too am running a 3Ware RAID controller (RAID5 right now). See the link and delete a few lines from the txtsetup.oem (or use Fernando 1's file) and you are good-to-go. Enjoy, John.

benbenno, that one is probably OK. I would suggest this one. At the top of the nLite forum is a sub-forum for AddOns and also RayanVM has lots of AddOns and Update Packs. These are just added to the nLite Hot Fix section (they are not CABs, but non-slipstreamed AddOns are). Be sure to add any IE8 updates after the AddOn for IE8. Enjoy, John.

benbenno, yes. My install is completely silent. We need more information, so, 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.