taltamir

Narrowing this down... I canceled the tweaks and removed components and this time IT WORKED.. Since I doubt that removing system restore or the useless documents did that I am going to have to assume it was the SFC disabling or the unsigned themes support. I cannot however perform further tests at the moment (since this was all on my roomate's computer and he is sick of me using nLite on it at the moment

PROGRESS UPDATE: I narrowed it down to either removing system restore, the useless documents directory, SFC disabling, or the unsigned themes support. This is actually an old bug, I remember having it since v1.2 or even earlier... I just never found out what it was exactly that did it before so i just gave up on doing ANYTHING AT ALL to my xp64 and simply used the unattented install option only to get a working copy of windows... I think I narrowed it down though: When using windows XPx64 pro corp: XP64 (No programs installed).ini causes no programs to be installed (no internet explorer, no media player, nothing, the computer is unusable) XP64 (CRC-02).ini also does not work and it does NOT recompress the cabs even though its set to max compression! Or rather, max compression claims to be set on by default and its on the default setting... I am gonna run a few more tests to see whats going on... but apperently its not cab merging.

Is there a patch or something out there that makes windows ignore WHQL driver signing and just use the latest driver it has regardless of weather its digitally signed or not? This money grabbing scheme has resulting in unimagineable amounts of neck pain for users whose drivers would just not install (or require them to confirm their agreement to install a non certified version 50 times over)

It would be really nice if there was an "all" button or the ability to shift select (to select multiple entries at once) on the language groups option in the unattended install window. I have to manually select each language every time I make a new preset... shift select would be ideal...

thanks for the reply but that doesnt really answer my questions. Q. Does it, or does it not, save space on the HARDDRIVE when INSTALLED to further compress the cabs? I am already familiar with the usefulness of it if you want to integrate stuff, and the fact that you can use classic interface and black background (which i do already). I just need to know if it actually affects the final install or only the size on the CD.

I am confused about the high compression option, does it result in a smaller INSTALL or only in a smaller CD? if it extracts it anyways I would rather it be "compressed" in store mode so that it installs fastest and it ends up not taking any more time. But if it actually changes the size of the final installation then it would be a good idea to use max compression... Clarifying this in the description would also be nice...

Its something that terminates when I tell windows to shut down, but abords the shutdown process. I can tell it aborts the shutdown process because nothing else shuts down, and I can run new programs. (which you cannot do while windows is shutting down). I also tried waiting ALOT of time and it didnt help... It always works the second time I tell windows to shutdown (i dont press the physical button, i use the shutdown option in the start menu).

I recently reformatted and now I have to tell the computer to shutdown or restart twice for it to do it. There is no noticeable action the first time around... Now this is ALWAYS the case, sometimes it works the first time (rarely). The odd thing is that I barely have anything installed so there is little that could have done that... If this is completely unheard of for nlite, then let me know and i will try reinstalling again, maybe it was a fluke and not a problem with nlite. If someone knows of it, a fix is welcome... Any idea what could have done it or how to fix this? I would rather not reformat, and I installed a bunch of stuff since...

i meant chkdsk... what do you mean delete it offline? winPE? Anyways, I already got rid of it by using unlocker: http://ccollomb.free.fr/unlocker/ It couldn't find anything to unlock, but it was able to force delete it anyways...

I have two folders that were created when I tried to force extract a corrupt ACE archive (set to not delete defective files). Those folders cannot be opened, moved, renamed, deleted, or anything for that matter. I can (now, i dont think i could before i started messing with it) rename the parent folders contianing them, so i isolated them in their own folder by renaming parent folders and moving any non corrupt stuff into a new folder with the old name. 1.I tried scandisk, but that didn't do anything (scandisk only ever worked for fat32... i never saw it do anything useful on NTFS...) 2.I tried del, erase, and rmdir from command prompt to no avail... 3.I tried changing the permissions from BUILIN\ADMINISTRATOR to my own admin account using subinacl, but that still didn't work... I used the following sytex for subinacl: subinacl /subdirectories C:\directory\*.* /setowner=machinename\Administrator And yes I am logged in as the administrator so this is my current user. Now from personal experience i just leave such files until the next time i format, but not this time, this time i am fighting and i am determined to kill those blasted things... so any advice is welcome...

security alrets always seemed absolutely and completely useless to me. there are always virii out there and knowing of a specific one doesn't matter.

If removing that file wasn't enough (or just for security's sake since viruses sometimes install eachother)... If it keeps on comming back through java? uninstall java and delete the java runtime user/settings files and folders. (you can reinstall it later when the outbreak is over). While you are at it, disable system restore (it might save some copies there aswell) Scan it from the online scanner housecall: http://housecall.trendmicro.com/ get the zonealarm trial and have it try and clean it: http://www.zonealarm.com/

1. Formatting is harmless 2. Only format usb drives as FAT32 3. You would have no problem using the extra space even after you install linux, just don't use it all up (as linux might need some of that space.

why does it delete error reporting? is it necessary for the install of .net or is it a personal preference?

I have been putting in the computer name in my nlite discs and have successfully installed extra computers with the same name as a computer on the network. Then after I log in for the first time I change the name. (although normally i just make a new custom disc for every installation using the latest nlite version and its unique computer name)

Aquire a non modified version of windows and modify it yourself WITHOUT removing components you need. There is absolutely nothing anyone else can do for you because the disc you got just doesn't have those files. nlite is meant to make custom installations with components modified, removed, or added. It is very useful, but it pretty much requires that you always keep an original and remake your nlite disc every once in a while to account for new versions of nlite or integrated components... If you don't have an original, tough luck.

Well, I am assuming its self explanatory as to WHY i would want windows to automatically ignore driver signing (or lack of thereof) and just install the latest driver it finds regardless if it is signed or not (without annoying the user with those awful "your driver is not signed and is dangerous!" promps AND requiring a manual install of the driver ). Can it be done with nlite or some other tool?

Thats what he is saying, he is saying you CAN figure out what was removed, and that he will be glad to tell you HOW to tell if something necessary was removed if you just tell him which components you do need. (unless i totally misread the post in which case, sorry )

Extremely long logons (in modern computers) are usually caused by lack of chipset drivers. This is especially true for nForce2 chipsets, those just take FOREVER to logon until you install the newest chipset drivers (some bug in the drivers that shipped with windowsXP). Go to www.nvidia.com and get the latest chipset driver pack, install, and tell us how long it takes to boot then...