Kelsenellenelvian

Yes

OMG Jaclaz! I searched for a long while and could not find ANY that were .img files they were all the danged "Bootdisk makers". Thank you very much!

OK I need to do some testing of 98se in VMWare But I no longer have a floppy drive . Can some kind soul out there make me a boot disk .ima or .flp from preferably ME?

Really? Is there a guide out there? I would like to know this too.

UPDATE YOUR THEMES!!! Many minor changes have been made to the theming files. The old ones still work, yet the updated ones look and work ALOT better!

Maybe you should ask them. It will have somethig to do with a missing codec or some simple crap like that.

Pretty major changes where made to the themes .html file in the last couple of versions! Please for the love of god if you are using a custom theme and everything looks like crap or is off, zip the theme folder up and post it here. I will update it. If your using a "Standard" WPI theme simply download a new copy from the site, delete your old and replace with the new copy.

Like this? Maybe you should just update your theme. (Its in the .css file.) ALL %oem% files where updated! Just pick the same one as you had before.

You CANNOT slipstream SP2 beta!

I think I get what you mean.

Ummmmmm WOW like 20 effin spaces??? That shouldn't happen, BUT I am glad it is working for you.

Sorry just tell me which installbg and logo you are using... Nevermind I will just make our graphics guru fix them all in the next coupla days.

You need a IE7 or higher integrated. Gimme the useroptions.js and the theme folder of the theme you are using and I will MOD the images so the show in an older browser.

No it's NOT a good idea to remove them! The integration process is built on the fact of them being there. You'll stuff up your whole disk.

There are no 64x drivers for your system. Please run CPU-Z and take a screenie of the first page then post it here.

OMFG! This whole damned time you could have just told us what type of PC (Notebook) it was...! Flip it over and tell us what the service tag # is.

We don't need to know the type of hard drive we need to know the type of CONTROLLER. What is the make and model # of your motherboard? If you dunno open your case and take out a torch (Flashlight) and then tell us what it says on it. Yes there is a SH*TLOAD of tiny writing but we need the bigger writing, it will say something like Gigabyte, MSI, whatever. Then on another place will be a random set of numbers and letters we need those 2. If all else fails then take a GOOD pic of the mobo with everything out of the way (Video card, cables and such) DO NOT remove the CPU!

I am having some trouble understanding the actual scope of your problem. However here are a few, common mistakes people make. Never use a PRE-nLited CD. OEM disks really suck and usually CANNOT be properly slipstreamed. Don't extract the service pack! Point nLite to the unmodified SP. Try, if at all posssible, to get ahold of a no-sp disk. Edit -- Saw your edit and see that you have a Dell OEM cd. Your chances of slipstreaming it have effectivly gone to near - ZERO.

I Hope you don't mean ME!

Then I got you wrong. Because you are registered in the group " Software developers" and you said "No, No (Been asked hundreds of times and the answer will always be NO!) It's to dangerous to have dozens of hacked up vLite versions." I thought you develop vLite and you knew what you were talking about. At least I'm sure now that I won't use vLite unless there is a possibility to check what it is doing. Yeah I develop Windows Post-Install Wizard. I just have been around for a very Looooooong time and been using nLite since the beggining. Plus I have LOTS of free time so I read most post in this forum.

?? You mean the top sestion where it shows the commandline? Or like shadowed in the main window? Did you notice in the bottom area where it displays a 1/39 type dealy?

When you select (Single driver) integration the txtsetup.oem file is the KEY file for sata integration. It's like the identifier. You most likely are select multiple drivers and nLite is picking up the file itself. I like to trim out as much as I can

Ya know a donation to nuhi would prolly help. Plus we all have real lives ya know.

OK take the x32 folder and add the txtseup.oem file into it. You will then have a folder with these files: jahci.cat jahci.sys jgogo.sys JMahci.inf txtseup.oem and point nLite to that folder, when you get a popup asking for txtmode or standard integration you MUST pick txtmode. Then off you go.

ALL run WPI solutions have been fixed! They now run at the designated time and also include the Office fix.