Jump to content

TranceEnergy

Member
  • Posts

    963
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by TranceEnergy

  1. I dont know about you guys but i think my nearly-done-no-it-cant-be-true xp 64 sp2 all updates at 140mb is quite good. I found that if i do some changes on xp 64 before i integrate servicepack+updates, the resulting image is even smaller. I also run the sfc disabled patch several times, which helps clean up 5-20mb each turn. However i firmly believe the way to have a truly light windows is to get portable software. Which suits me just fine anyway. Also to really get the xp install really light, you have to get your hands dirty and start figuring out what files you can add to remove list in nlite. If i can break under 100MB on this xp x64 install, then i will be satisfied, maybe for a month...
  2. I for one, have found a good routine when making nlite install iso's that works pretty darn good for me. What i usually do is to start with a clean windows, with NO service pack, no updates, no thing, pure clean simple. I then apply unattended settings,no patches, and tweaks. The point here is to change the PATHS for windows. So that windows folder is named XP f.ex ( i actually name it just X), PF for program files, U for documents and settings. You see? After this is done, i save the preset naming it something like XP-PREP. I then apply any service pack. Then reapply the preset. Then update hotfixes. Reapply preset, remove stuff, reapply preset. I think you understand yes? Anyway it works great. On xp x64 there was long a problem with fresh install showing 4 folders for program files with the original take. F.ex it showed PF, PF (x86), program files (x86) and program files (x86)(x86). The theory I have here, is that it is FIRST best to DISABLE anything you will THEN REMOVE. That way, in my head, lol =)), windows thinks aha- ok its disabled, and go about on its business. Now this may all very well not be needed anymore as of newer nlite version, but i find it to work really good still. And at least if i do rename program files, with 1 step nlite routine, i will have several program files folders as mentioned. In my setup, i get just the folders i should have. TOTALLY off topic, but my mind is retarded, sorry. =)
  3. This is simple. Buy another harddrive , 1tb drives here are cheap, get a decent usb2/fireware box to keep it in, with preferrably built in ac adaptor or such so u dont have to drag that along to. Simply connect usb/fw to computer, start backup, disconnect drive, put it back in the closet/drawer, and put a small note to self, backup done.
  4. It is, Alltho i was a bit confused, and still am, about this subject too. You see there's remote desktop client, services, and terminal. To remove the ordinary remote desktop, you would have to get rid off terminal services, and then you would also have to skip the remote desktop update, which on x64 is WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU. Probably WindowsXP-KB925876-v2-x86-ENU or something for 32bit xp. The problem is however, if you are going to do this, you have to face the fact that you would have to do a very minimal nlite install, which can be a good thing, but lots of stuff relies on terminal services. The solution to this, isnt quite clear, I suppose one could resource hack the files into submission and get rid of remote desktop completely but keeping terminal services, but thats a lot of work. Ideally tho, one would do this but it would take a lot of work,time, and doesnt fit well with updating windows, which you can more or less forget, as you would have to extract every MS-KB and update windows manually. It would get complicated, really really fast. Unless you happen to be a programmer and decides to code such a tool. and no i dont think Nlite will ever do this =(
  5. Quick reply, but i have always gone into the driver inf. files and deleted anything not actually needed for the driver/hardware to function. Unless im doing bugtesting etc. Uninstall.exe type of files, are definitively not needed. Nor help files if you are never going to read them. There's just so much bloat. A GREAT example of bloatware in drivers the Creative X-FI drivers. I have been running computer with realtek hd audio for quite some time, and thought i'd do some benchmarks and test if the sound quality was really any better with the x-fi. I didnt think so. But anyway, then i got a flashback. If you have these drivers installed, you are in for a small nightmare. Turns out even Guru3d.com has made a tool to remove the drivers. Which i tried, and it didnt remove even half of all the files left in windows folders and registry. It took me 15 minutes of manually deleting stuff from registry to get rid of it completely. The only times you should keep something is if it is actually needed for compability/stability, alltho u wont ever 'use' it yourself. Unsigned driver installations isnt a bad thing, it means you've done your duty =)
  6. Hello folks. As in topic, I seem to remember having a cool program that didnt rely on MS/Windows to surf lan, but cant remember the name atm. Anyway, a lot of services are dependent on computer browser/firewall, or vice versa, so i was wondering if someone had a workaround to this that didnt rely on having the bloody firewall integrated in windows?
  7. Dont know if the thread has this, but if u think back to XP SP1, the TCP/IP limit was 65536 connection. Thats a big difference to SP2 that started the max10 connection BS, if i can say so. Because it really is. I for one have never had any spyware,viruses or such that this limit is supposed to hinder, at best.
  8. Lol, so say 1hr per version or something? I would never get any version of windows finished in time at that speed. Here it takes about 5 to 10 minutes. Ramdisk forever..
  9. I thought this was kind of interesting. I've always used to nlite windows to the absolute bare minimum, get rid of +com, mdac, wmi etc. So, how did windows do with the exact opposite? As bloated as possible? I used Windows xp x64 sp2, pre integrated all fixes etc, .net 1.1 to 3.5. Every gawdamn feature you could imagine enabled. All windows services set to automatic. Now please bare inmind this test was done on a 8gb ddr2 amd dualcore, so it can handle it. I also enabled every protocol for network driver and so forth. However i had done all TWEAKS possible, from nlite setup. As it turns out, I could'nt for the life of me get windows to slow down or what not. The funny thing is, windows booted quite fast and ran userlogin immidiately, allthough win kept loading because of the excessive amount of services enabled. This is kind of short summary, but it totally changed my view on the matter. Get rid of things that annoy you, and try to live with it. I guess the reward is a lot higher compability/possibly stability issues, alltho i never had a crash on my nlite installs for a couple of years now. I will say this tho, there is nothing, NOTHING like the feeling of sitting infront of an uber-responsive heavynlited install. Dammit... Now i want to reinstall everything again... OT: is .net 1.1 really needed anymore? Wouldnt 3.5 redistributed be enough?
  10. I have just got this same issue. However, i one the other hand have not removed anything by nlite, or used litestep, on this install.
  11. IF you are saying you want to have PF & DS and any other folders on DIFFERENT volume then your Windows folder, setup as default/standard from within the Windows Installation Image, then you must be aware of the primary partition setup that the "bluemode" text setup routine uses. If you have f.ex 2 drives like this : Harddrive 1: c:\ <- Primary d:\ <- logical e:\ <- primary Harddrive 2: S:\ <- Primary then when you are in textsetup, then S:\ will be seen as D:\, e:\ as E, and D:\ as f:\. At least the logical partiton will be,should be,least prioritized in the "logical" volume letter setup. S:\ would anyway become D:\. Unless of course the Harddrive 2 was on a separate controller and f.ex the cd-rom drive was on the same, or at least higher ranked controller then Harddrive 2. Hope you get the picture. I don't know or have heard of such a thing as to have any other routine/setup for this. As to how this is possible, yes it is.Have I done it? More then I care to count Let's kill this Pf(x86) issue right away. You must have Program files folder that is for 64bit and the x64 equivalent for the 32bit variant. However, if you are installing any app at all that don't have both, you may install it where ever you like. The problem is, that in theory, in todays program INSTALLERs, there is NO actual support for this. I haven't seen any program that do. That is, a program installer that raises the questions: Where do you want the 32 bit files installed and where should the x64 variant go? It just asks where do you want your program to be installed... However, if you are willing to walk on the wild side, it is in quite possible to remove all 32bit files from windows xp 64 bit. But know, you will have your work cut out for you. And program support would be small, since there would be no such thing as 32bit support longer on the system. In current state the 1.0rc7 (i always forget if its 1.0rc7 or 1.07rc..) does allow for the program files and program files(x86) to be changed. But, i have found it to not truly be fully correct, as have others. In my case, i rapped up all .cab files (*.*_ files <-)) and made necessary changes to my chosen pf and pf(x86), which might as well be p1 and p2 for that matter. Nlite has gone a long way with 32bit, is my overrall perception, but is not quite there yet with x64bit. But it's going very well imho. your variables are correct, though u need to cut the (x86) part for the normal x64bit program files/common files folder. You could, as hinted, name the paths to be almost anything. Anything is possible, with enough time and effort. Not to mention dedication.
  12. I can verify that this is still an ISSUE, at least for x64.
  13. I have been waiting for RC8 for Nlite for a while now. Will give this a go. As it turns out, the support for x64 in nlite isn't exactly trust worthy, or up2date even. Is powerpacker x64 friendly?
  14. I have successfully managed to get Windows Xp Pro x64bit running with 1 service as well. Or zero services if i disable the dhcp and use a third party. It's doable, and frankly it leaves a faster system too...Even for benchmark tests.


×
×
  • Create New...