LeveL

Hehe, some people still refuse to go from Win2000 to WinXP Considering this is the first ever release of vLite it already removes enough for me! But I think with Vista - one of the main things or in demand things people would love is if the 512Mb RAM requirements and the fact that you need a 15Gb disk or bigger could be eliminated. Thats pretty sick, especially when Vista runs pretty smoothly on under 256Mb RAM in VMware... if you drop the RAM down after install that is. It needs to be on 512Mb otherwise it won't install but then it can be dropped down to as little as 224Mb... whats that all about? I demand an answer from a M$ official! I just knew there had to be a good reason... my fault for using my weeks old v5384 Have a look at the bottom of this screenshot from vlite.net, if all components are selected you can slice a massive 4666.9MB of stuff from an install http://www.vlite.net/img/shots/ss2.png How big is Vista on a normal install though, about 8Gb or something (Ultimate)?

OK retested again and it removes the components, then about 30% through "Cleaning Up" vLite just vanishes off the screen and the process is not running in Task Manager. I go to delete the contents of the source folder and the WIM image along with many files in the temp folder are locked, I guess thats because the SYS file that opens up the WIM images is still holding onto them? Remember though I am running this on the Beta (5384) of Vista, which is probably six weeks old by now.

I am testing on Vista Ultimate Beta 5384 and left it to do its stripping, went to check on it and the vLite process had completely closed, so I re-opened vLite and browsed to my source folder and it said: Error accessing image. Error: 32 It started taking out the languages and other stuff I chose but I didn't watch it do its stuff so I can't say exactly when it crashed out. I will re-test it and post back. BTW Nuhi this looks awesome already! --------------------------------------------------------------------------- Unrelated, but WTF is going on with MSFN, why have I got a list of links to posts in this topic at the bottom instead of just the normal post after post layout? Its like this at the bottom: Has this happened right across the baord or is it just me? Tried changing it in "My Controls > Board Settings" to show 30 topics per page and 30 posts per page but its not changed anything. I hate it when it does this!

No it won't be... the only related thing I have removed in nLite was "Images and Backgrounds". I would rather get the start menu to be set on small icons to be honest, people spent weeks, months even, finding that hex change in XP, I don't think the answer even exists for Windows 2000

W0000000000000000000000t Thanks for this - time to get to work on it! B)

It looks like the start menu logo is missing: However, this is what the top of the logo looks like anyway so I am not sure its still displaying it and only the top of it - normally the start menu is twice as high as this. What I want to do really is make it set to "Show small icons in Start Menu" but I have tried the Windows XP reg tweak and it is not the same on Windows 2000. That would give a miles better look and also cut the problem of the black space out too... The reg tweak is driving me nuts for this, it will most probably be two hex numbers like it is in XP but where are those hex numbers?! The XP tweak for small icons in start menu is like this: However this is not the case on Windows 2000 Help! OR Can anyone tell me what image file shows that start menu logo so I can keep the DLL it is a part of? HINT: Its not a GIF image, its not a BMP image, or JPG or any image format so I guess its inside a DLL file, which DLL file though? HELP HELP!

Thanks for the quick reply. Well, I was being lazy and not wanting to strip it again but, its fairly easy the way I have got things set up... can HFSLIP also integrate these... MDAC253-KB911562-x86-ENU.exe Windows2000-KB891861-v2-x86-ENU.EXE Windows2000-KB900725-x86-ENU.EXE Windows2000-KB917008-x86-ENU.EXE Windows2000-KB917344-56-x86-enu.Exe Windows2000-KB923191-x86-ENU.EXE Windows-KB890830-V1.22.exe The thing is I have already integrated every other hotfix with nLite, even my "source" folder has them integrated, eeeeek! Maybe using HFSLIP after nLite might work? Other option is to totally start again with Windows 2000 SP4 and slipstream the dozen upon dozens of hotfixes in with HFSLIP then have that as the source folder and start stripping (a copy of) that. Eeeeesh its had IE6 and DX9c integrated with HFSLIP a long time ago, I think I got to start all over again but nevermind.

There are a few small hotfixes that nLite will not integrate into Windows 2000 like the Jscript hotfix and Malicious Software Removal Tool hotfix, but these are only small. The problem is, there is a HUGE hotfix called Windows2000-KB891861-v2-x86-ENU.EXE that is over 30Mb (it seems to contain half of system32 when I look whats inside it!) and nLite does not give any error to say it has not integrated it, but it does not integrate, the hotfix is still needed on Windows Update. I don't want to add 30Mb to my ISO (I could just use the /Q /O /Z switch to install it) and I am not sure about using the HFSLIP method after using nLite on the OS, is there any way to slipstream this hotfix into the source without having to add the 30Mb file to the ISO? This "Rollup Update" contains a lot of updated files, like I say if it is slipstreamed properly somehow, I am sure the source won't increase in size at all: uniproc *DIR*, update *DIR*, wms *DIR*, acctres.dll, adsiis.dll, adsldp.dll, adsldpc.dll, adsmsext.dll, advapi32.dll, afd.sys, asp.dll, authz.dll, autochk.exe, basesrv.dll, browser.dll, browseui.dll, cabinet.dll, callcont.dll, catsrv.dll, catsrvut.dll, cdfs.sys, chkdsk.exe, ciodm.dll, clbcatex.dll, clbcatq.dll, cluscfg.exe, clusocm.inf, clussvc.exe, cluster.inf, cmd.exe, colbact.dll, comadmin.dll, comrepl.dll, comsetup.dll, comsvcs.dll, comuid.dll, crypt32.dll, cryptdlg.dll, cryptnet.dll, cryptsvc.dll, cryptui.dll, csrsrv.dll, dao360.dll, default.asp, dhtmled.ocx, directdb.dll, dnsapi.dll, dnsrslvr.dll, dplayx.dll, dpwsockx.dll, dsexts.dll, dsprop.dll, dtcsetup.exe, dxmasf.dll, empty.cat, es.dll, eventlog.dll, expsrv.dll, fastfat.sys, faxui.dll, fltlib.dll, fltmc.exe, fltmgr.sys, fontview.exe, ftdisk.sys, gdi32.dll, gpedit.dll, grpconv.exe, h323.tsp, h323msp.dll, halmacpi.dll, hfsecper.inf, hfsecupd.inf, hhctrl.ocx, hlink.dll, html32.cnv, httpext.dll, hypertrm.dll, iischema.dll, iisext.dll, imgview.htt, inetcomm.dll, inetres.dll, inseng.dll, ipnat.sys, ipnathlp.dll, itircl.dll, itss.dll, jscript.dll, kdcsvc.dll, kerberos.dll, kernel32.dll, krnl386.exe, ksecdd.sys, linkinfo.dll, llssrv.exe, localspl.dll, lsasrv.dll, lsass.exe, mdac.cat, mf3216.dll, mountmgr.sys, mpr.dll, mq1repl.dll, mq1sync.exe, mqac.sys, mqads.dll, mqclus.dll, mqdscli.dll, mqdssrv.dll, mqmig.exe, mqmigrat.dll, mqoa.dll, mqperf.dll, mqqm.dll, mqrt.dll, mqsec.dll, mqsnap.dll, mqupgrd.dll, mqutil.dll, mrxsmb.sys, msasn1.dll, msconv97.dll, msdtclog.dll, msdtcprx.dll, msdtctm.dll, msdtcui.dll, msdxm.ocx, msexch40.dll, msexcl40.dll, msgina.dll, msgsvc.dll, mshtml.dll, msiexec.exe, msjet40.dll, msjetol1.dll, msjint40.dll, msjter40.dll, msjtes40.dll, msltus40.dll, msmq.cpl, msoe.dll, msoeres.dll, msoert2.dll, mspbde40.dll, msrating.dll, msrd2x40.dll, msrd3x40.dll, msrepl40.dll, mst120.dll, mstask.dll, mstask.exe, mstext40.dll, msv1_0.dll, mswdat10.dll, mswrd632.wpc, mswstr10.dll, msxbde40.dll, msxml3.dll, msxml3r.dll, mtstocom.exe, mtxclu.dll, mtxdm.dll, mtxlegih.dll, mtxoci.dll, mup.sys, nddenb32.dll, netapi32.dll, netbt.sys, netcfgx.dll, netdde.exe, nethood.htt, netlogon.dll, netmon.exe, newdev.dll, nmcom.dll, nntpfs.dll, nntpsvc.dll, nscm.exe, nsiislog.dll, nsisapi.exe, nspmon.exe, ntdll.dll, ntdsa.dll, ntfs.sys, ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe, ntlanman.dll, ntoskrnl.exe, ntvdm.exe, ntvdmd.dll, nwrdr.sys, odbc32.dll, odbcbcp.dll, odbccp32.dll, oeimport.dll, ole32.dll, olecli32.dll, olecnv32.dll, osloader.exe, pngfilt.dll, profmap.dll, psbase.dll, psxss.exe, quartz.dll, query.dll, rasapi32.dll, rasdlg.dll, rasman.dll, rasscrpt.dll, rdbss.sys, rdpwd.sys, remotesp.tsp, ris.vbs, rpcproxy.dll, rpcrt4.dll, rpcss.dll, samlib.dll, samsrv.dll, scecli.dll, scesrv.dll, schannel.dll, scsiport.sys, seclogon.dll, services.exe, sfcfiles.dll, shdocvw.dll, shell32.dll, shlwapi.dll, sp3res.dll, spmsg.dll, spoolss.dll, spoolsv.exe, spuninst.exe, spupdsvc.exe, sqlsrv32.dll, srv.sys, srvsvc.dll, system.adm, tapisrv.dll, tcpip.sys, tshoot.ocx, txfaux.dll, udfs.sys, umandlg.dll, untfs.dll, updcustom.dll, url.dll, urlmon.dll, user32.dll, userenv.dll, vbajet32.dll, vbscript.dll, vdmdbg.dll, w32time.dll, w32tm.exe, wab32.dll, wab32res.dll, webvw.dll, win32k.sys, winhttp.dll, wininet.dll, winlogon.exe, wins.exe, winsrv.dll, wintrust.dll, wkssvc.dll, wldap32.dll, wlnotify.dll, wordpad.exe, wow32.dll, write32.wpc, xolehlp.dll. This lot is more than 90Mb It is 25% of the Windows folder! If theres no way to do this I will have to just add the big lump of a 30Mb hotfix and install silently before last reboot.

I also integrated IE6 and DirectX 9c a while ago using the HFSLIP guide, it works perfectly but can you use nLite on that afterwards? I vaguely remember it doesn't like nLite, or nLite doesn't like it, depending on which side your bread is buttered. All I want to do to it really is re-compress the cab files and remove a few languages here and there, hmmm, guess I will just have to try it out.

The common mistake most people make is thinking having more RAM will help. Come on this is Windoze we're talking about - if you have 1Gb of RAM, Vista will use 800Mb of it. I can guarantee that if you had 2Gb RAM, Vista would use 1.6Gb of it and if you had 4Gb RAM Vista would use 3.2Gb of it, because thats how it works, XP is the same. If you install XP on a machine with 64Mb RAM, it will run, on a wing and a prayer and theres no "Fast User Switching" possible on 64Mb RAM but XP will run. So then why is it - if you install XP on a system with 512Mb RAM it uses more than 90Mb? Because thats the way it works! It doesn't use 90Mb+ on a system with only 64Mb RAM because thats impossible! This is what really sucks about Windows, it just rapes your resources at will. No I am no fan of Linux, I actually think it sucks a lot more than Windows, but at least Linux runs on something like 32Mb RAM and if you have 4Gb RAM it STILL runs on the same - 32Mb RAM. So when I ran Vista (Beta 2) in VMware, installed on 512Mb RAM (because it WILL NOT INSTALL on any less than 512Mb RAM) then powered it off and dropped the RAM to 224Mb it ran just as smooth as it did on 512Mb RAM. Its an illusion to think its "slow" when you have 1Gb RAM. No, its just using 800Mb as it pleases. If the Vista version of nLite is the same as the NT one then you will be able to cut the RAM in half to about 400Mb. Vista has 40 running processes (I think) I mean come on - FORTY processes? What the hell is that? Why does it run so many? Get it stripped out - down to maximum 20 processes and about 50% of the services ripped. Asking "Do you want a version of nLite that supports Windows Vista?" is like asking "Do you ever want to breathe/drink water/blink again?" Does a bear s**t in the woods? Is the pope a Nazi? Yes to all

Freeze ups and slowdowns are usually the RAM. If you have a floppy drive, get memtest and test the RAM... http://www.memtest86.com/memt32.zip Or burn the memtest ISO to a CD-RW (don't waste a 700Mb CD-R on this).... http://www.memtest86.com/memtest86-3.2.iso.zip Also check in Device Manager (Start > Run > devmgmt.msc > OK) under "IDE ATA/ATAPI Controllers" double click it and double click again the first item, example on my system its "NVIDIA nForce3 250 Parallel ATA Controller" then click the Primary Channel or Secondary Channel tab depending on which your DVD drive is, then have a look under "Transfer Mode" and it should say UDMA 2, or DMA 2 or Multi Word DMA 2 - just as long as it is not on "PIO mode" then its OK. PIO mode is what makes DVD's burn slow, it is limited to 17Mb a second I think, something crappy like that, many times it does just quit halfway through a burn if its on PIO Mode.

Kaspersky AV all the way. The reason ---> highest detection rate. Its really that simple. You know when someone doesn't really know their stuff when they call Norton Anti-Virus "Anti Norton Virus". You know sometimes I wish there was such a thing. I used Norton "Systemworks" 2001 in 2001 and since then I ain't touched it with a barge pole. I realised theres way better alternatives like Symantec Corporate v8, v9, v10 (used them all, all are good) or now Kaspersky AV, it wipes the floor with Norton. Norton is like Mac Donalds, where Kaspersky is a piece of fine steak!

I want one! (the doll not the laptop) I thought it was going to be this clip... http://crave.cnet.co.uk/video/0,139101587,49284379,00.htm

You can get XP down to about 360Mb as the installed WINDOWS folder, after that you start to lose serious functions, like MDAC, Jet Database, Printer Support, Windows Management Instrumentation. As an ISO it probably translates to about 160Mb. To lose things like Printer Support (Print Spooler Service) and ability to use webcams and digital cameras (Windows Image Aquisition service) then yes, you can get the WINDOWS folder down to maybe under 300Mb and a 110Mb or 115Mb ISO but then, its not going to really support the things you'd expect it to. By default Windows XP uses up 1200Mb of disk space and its a 400Mb+ ISO!

You're right, how bizzare. I don't know about stopping the populating of the icons but you could run this in a CMD or BAT file on the new user profile to delete them... DEL /F "%USERPROFILE%\Application Data\Microsoft\Internet Explorer\Quick Launch\Show Desktop.scf" DEL /F "%USERPROFILE%\Application Data\Microsoft\Internet Explorer\Quick Launch\Launch Internet Explorer Browser.lnk" Might not be the exact names since you're on Win2000 but be aware that "Show Desktop" is not a shortcut, it is a .SCF file not a conventional .LNK shortcut.

Its April 1st, right? Nope, November 15th actually so erm....... One of these days Microshaft will licence themselves out of being able to release any of their own software then... yay!! NO MORE Microsoft software! All their code is stolen from other companies [cough]STAC DOS[/cough] anyway, why do you think they charge so much money for their software? Its to pay off all the multi million dollar lawsuits. Well, if Vista is nLiteable then I can maybe live with it, but theres no way I am using Vista untweaked/unmodded. I still think "nLite VE" would be the best name, the main thing being not to deviate away from the word "nLite" because it is FAMOUS now! Everyone knows the name. Its bad news changing a name I think but hey, its only what I think, why should that matter. Heres a tip that shows how bloody sneaky Microsoft are: Install Vista in VMware, you need to set VMware on 512Mb RAM m'kay, otherwise it simply will not install. Now, when its installed, power off VMware and drop the RAM right down to as low as 224Mb and start it up again. What do you notice? Not only does Vista RUN on 224Mb of RAM but it runs just as smoothly as it does on 512Mb, so in this case, what possible reason, however flimsy, could M$ use to justify an OS that refuses to install unless the machine has 512Mb RAM but then that runs perfectly well on 256Mb RAM, less in fact? Can anyone answer that question? Like ummm, a Microsoft spokesman? No because he/she will say the licence forbids you to install on a virtual system! OMFG! Its not a joke either! Is THAT why its "forbidden" because people like me will NOTICE things like the hardware RAM SCAM? I can't wait to be able to strip Vista down! Strip it to within an inch of its life! B)

I was getting "NTLDR corrupt" please press F3 yada yada, so I used the cracked setupldr.bin posted here and now I get "NTDETECT failed", hmmmmmm... do we need a cracked ntdetect.com file too?! Using Server 2003 SP1 doing a multi boot OS.

OMFG I got it to work! B) Sorry for sounding arrogant but it wasn't anything thats been suggested here. Theres a simple reason I was getting the EULA.TXT not found message - because I didn't re-edit the txtsetup.sif file, doh! It works perfectly now, can't believe I have crammed XP and Server 2003 onto a single CD, the ISO is only 390Mb and each OS is heavily stripped out - yes, WITHOUT the Manual Install and Upgrade option. Heres how its done, its actually incredibly easy... 1 - Follow the flyakite multi boot guide and make your AIODVD as normal. 2 - Now strip anything you want from any OS, example, you want to strip XP, just point nLite to D:\AIO-DVD\SETUP\XP\Professional\ and strip it as you normally would. 3 - Now the trick! Go into D:\AIO-DVD\SETUP\XP\Professional\I386 and copy the file txtsetup.sif to your boot folder for that particular OS, in this case with XP, following the guide, it would be the D:\AIO-DVD\PRO1\ folder. It will already contain a file called txtsetup.sif - just overwrite the old one, its useless now that XP is stripped with nLite. 4 - Now you have to open that file D:\AIO-DVD\PRO1\txtsetup.sif and Ctrl+F and find SetupSourcePath. Just like the flyakite guide tells you, you have to enter in the path to the setup source, in the case of this XP and PRO1 it will be changed... FROM: SetupSourcePath = "\" TO: SetupSourcePath = "\SETUP\XP\Professional\" 5 - Thats it!!! For unattended, just move the file winnt.sif from I386 into the PRO1 boot folder and it will work. So in summary, all you're doing is stripping with nLite, then copying the file txtsetup.sif from I386 to the relevent boot folder for that particular OS, then re-editing it back to how it was again to reflect the right setup path. So easy when you know how!

OK thanks, I vaguely remember this now, theres 7 instances of I386 in the S2K3 version of setupldr.bin, instead of 4 instances. You mean leave in "Manual Install and Upgrade" ??? This is what I am trying to find some way around, not having to leave Manual Install and Upgrade in just to do the copying of boot files via WINNT32.EXE.

I can make a multi boot DVD of 2000/XP/Server 2003 and it all works if these are all full installs. If I strip the OS's with nLite, it won't work. The boot files (in ENT1 and PRO1) are as they should be, except I have replaced the txtsetup.sif file with the one from I386 - it still won't work... XP said EULA.txt cannot be found and Server 2003 said NTLDR is corrupt... is it possible? Break these 3 OS's down to 230Mb each and you could in theory have nLite'd 2000/XP/2003 on a 700Mb CD. I wish it was possible! I searched every page for nLite in the Multi Boot section... http://www.msfn.org/board/index.php?showtopic=77922 - Posted in the wrong place http://www.msfn.org/board/index.php?showtopic=67030 - Same again, an aimless and off topic post http://www.msfn.org/board/index.php?showtopic=66937 - Not sure why this one is in the multi boot section since it has nothing to do with multi booting Windows. http://www.msfn.org/board/index.php?showtopic=50430 - Does not really go into any detail and the post is from July 2005 anyway http://www.msfn.org/board/index.php?showtopic=23149 - Hmmm, July 2004... says keep manual install and upgrade but believe me I have been through all that, it doesnt work. If you strip XP with nLite, the txtsetup.sif goes from about 400Kb to about 170Kb, it is the list of EXE and DLL files needed - the PRO1 boot folder on the root of the ISO also has a txtsetup.sif file, so I copy the small (correct) SIF file from I386 to the boot folder but it just doesn't work! Is there NO possible way to do this? Want to put XP and Server 2003 on a 700Mb CD.

I have done a multi boot a while ago manually and remember that you need the boot files to do this - in other words, you have to fool it into thinking you're installing Windows, then get the boot files - if you strip the OS it doesn't work so the simple question is - can you make a multiboot XP/2003 with this program IF its been stripped out with nLite?

I don't understand it. How does this work since all the files are extracted? Why do you do this bit: 5.) create a copy of the original inf file as Cupdate.inf I keep getting the error: "The version of Windows you have installed does not match the update you are trying to install" Why do you run "update.exe" and not the batch script? Oh man - can't someone just upload a fixed version of this for Server 2003? Sorry, I must sound lazy there but I have been trying to do this for more than an hour and its not happening. If anyone has a working version of WMP11 final for Server 2003 can you upload it to Megaupload please?

SMSS.EXE only has "Version Info" in Reshacker. "Windows NT Session Manager" I guess get all the .EX_ files and look at them all?!

Hmmmm, then it says "NTLDR is corrupt, the system cannot boot" I didn't touch NTLDR though! Maybe its best to just not even bother eh? It does not mention the name of the OS in SETUPLDR.BIN where it appears in the top left corner on the blue setup screen. "Windows XP Professional setup" does not appear anywhere in SETUPLDR.BIN aaaaaaaaaaaaaaaagh!!!!

Before anything else when you boot from a Windows disc you get the blue setup screen with the following: It says Windows Setup underlined in the top left corner with the message Press F6 if you need to install a third party SCSI or RAID driver... at the bottom, followed by the Setup is loading files message when all the other support for hardware loads in initially. Then it says Setup is starting Windows at the bottom. Then at the top it says Windows XP Professional setup (underlined) with the text The following list shows the existing partitions and unpartitioned space on this computer Then you press D/ENTER/L/UP/UP/ENTER or something like that to delete the existing partition and start formatting the partition (well OK I always do!) and then you get to a screen saying Please wait while Setup copies files to the Windows installation folders. This might take several minutes to complete. Then under that it says Setup is copying files... with a progress bar. The whole time it always says the same Windows XP Professional setup (underlined) at the top. What I am asking is 1 - Is all this text a part of the same EXE or DLL file? 2 - If so, which file? I want to make the ultimate customized setup! I have already ResHacked the file SYSSETUP.DLL that allows you to change the Windows screens as it installs (I am using classic setup done with nLite) but now I want to work on the very first initial text mode setup screens, these are not GUI based though and I am not sure (I actually have no clue) where this file is, whether it is a cabbed file or not (I wonder how it possibly can be since it runs right away?) HELP!