GrofLuigi

Some files of that component(s): cscdll.dll cscui.dll mobsync.dll I'm sure there are more. Put in system32, register them. Maybe try with Dependency Walker to see if they depend on any others... And of course, ProcessMonitor might help too. GL

XP: Hard drive restores APM value after returning from standby mode (entered when the timeout of monitor power down expires in Power Options; no other timeouts defined). I guess the controller driver is not consulted then (only on boot). QuietHDD is necessary after all (this was one of its strengths and reasons for existence). GL

Nlite uses mkisofs.exe for those functions (burning, creating iso), which is ported from Linux, but I don't remember the exact version (or maybe it was compiled by Nuhi?). I vaguely remember some problems with it in early versions of NLite... I think the best way to use it would be to let NLite create the ISO (as majority of users do it that way and haven't reported too many problems, so I guess it's the most widely tested function) and burn the ISO with the tool you're comfortable with. *Edit: And if you posted this report in hope of bugfixing, read johnhc's post above mine. The most important thing about this is that NLite is closed source and Nuhi hasn't been active about it for quite some time. The most we can do is hope and pray. GL

AAM - Automatic acoustic management APM - Hard Disk Drive Advanced Power Management The problem: I was annoyed by constant drive clicking (parking head) on my laptop (Intel ICH9M Sata AHCI controller). And I was not alone, judging from many user reports and questions on different forums. The drive in question is Seagate Momentus ST9250827AS. The solution: I tested hdparm and HDDScan, and finally settled for QuietHDD, which suited all my needs. But the little bug was still biting me and wouldn't leave me alone. During one bootlogging session with RegMon (yes, Procmon didn't show it - it either starts later or it was my filters) I discovered... The final and very elegant solution (for me): REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters] "Port0AAM"=dword:000000fe "Port0APM"=dword:000000ff "Port1APM"=dword:000000ff "Port1AAM"=dword:000000fe These values are suitable for my needs - to turn off AAM and APM - get rid of clicking. Someone else might select other values. I used the ones which worked for a long time for me - taken from QuietHDD. Port1* are thrown just in case, since I don't think the DVD drive will mind. Intel Matrix Storage Manager needed (version 8.9.4.1004 but I see no reason it wouldn't work on other versions), tested on XP/2003, might work on other Windows too (but I didn't notice the problem during my brief Vista testing so it's possible it "knows" how to control AAM/APM - or it constantly accesses the HDD so it doesn't have time to park ) In any case, it needs more testing (for other values), if anyone cares. GL

Have you rebooted before verifying the CD? Or tried it in another computer? Test mode is a feature of (every?) CD/DVD writer where a procedure of complete disc burning is performed, without actually switching the laser on. As far as the OS is concerned, the disc has been written. Depending on many conditions, a simple eject/load might not "convince" the OS to reread the disc. The test mode under normal circumstances doesn't depend on the burning program used (in fact, most of the CD/DVD writing operations don't - the burner is kind of a black box - just accepts commands and does its thing). Sorry if you knew this. But it is also possible you have indeed discovered a bug. GL

PWRON After PWR-Fail? I've seen many other wordings. GL

Then they should change the name to something like "hide-and-seek orb"? Menu (as in restaurant) implies displaying everything the "house" has available for you and you choose from the list. GL

Unrelated: Boot and Shutdown-Disable saving Last Good state at boot is your way out when you can't boot. Don't disable it. Even I, with multiple backups and rarely installing software, don't dare to disable it. GL

There's not much work done (not much changes) in your preset, but here are some observations of mine: 1. You are working on SP3 but don't integrate SP3? It shouldn't be a problem, but maybe IE7 requires it? Also, double check what (version, build?) is your IE7 and whether you can integrate it directly or you need an addon (I don't know, never done it ). 2. Is the theme you're integrating signed? If not, you need to do UXTheme patch and/or SFC. (again, never done it ). GL

That's 71.84 (recommended by NVidia if you search on their download page), but I still think it's better to find older version (archive). Even downloading and reinstalling the same version might help. I remember drivers of that time were somewhat difficult to uninstall, so proceed with caution. If it's properly installed, it should at least work, but if it doesn't, that indicates some other possible problem with computer that old. Also, maybe DirectX should be updated? And this topic better be moved to Windows 9X forum, someone there might provide better help? GL *Edit: typos

Which OS? What version of drivers? From memory, (it was a long time since I had the card), ForceWare drivers would allow to be installed on that card up to version 7X.XX, but there is no benefit in doing so (they had only optimizations/functions for later generations of Nvidia cards), the best (fastest and most compatible) version of the drivers for that card was Detonator 2X.XX (26?). I write this from memory, so it might not be so accurate. GL

It's not always mup.sys, that's just the last driver that's displayed on that screen. There was a page from Microsoft (or a blog) explaining this, but I am unable to find it now... My point is, it could easily be another driver, so more information is needed... And/or more advanced troubleshooting techniques, whatever they might be. GL

Right here is your best bet. But file manager is something else, there isn't one solution for all because every program uses different installer. UE has some shell integration features. Don't know if it works on 7. GL

Top 5 offenders from my experience: 1. Autoplay (not autorun, kill it in hklm/system/ccs/services/cdrom/autorun=0) 2. WMI (disable the service and live with the consequences) 3. DHCP (set static address, disable the service; some activity still remains if icon is left in tray) 4. Network Location awareness (disable the service and live with few benign issues) 5. Wireless service (no cure). Assuming the usual suspects (indexing, virus/antivirus) are out of question. GL

From empirical experience (read: fiddling with ProcMon): YourApp.Exe tries to access Internet. (I'm not sure what is the exact trigger - winsock, winhttp or something else... I think it's urlmon.dll; some apps use Internet without triggering FeatureControl). The Authoritae (I'm not sure who it is, in my case it isn't Group Policy since gp*.dll have been thoroughly nLited + manually eradicated; again I think it's urlmon since it's the last thing queried before the calls to Feature*) decides to give subset of controls to YourApp.Exe (I've seen different Feature_* queried for different apps; might be only my imagination) based on what operations YourApp.exe requested? (wild guess again). Then YourApp.exe queries the subset of FeatureControl\Feature_* it received and if there is a YourApp.exe dword in there, it uses that; if not, it uses the * dword (if present). I pray this post of mine makes sense. But Microsoft's documentation isn't too much more understandable (to me)... GL

How to resurrect an ancient thread: 1. Download DirectX redistributable. 2. Extract it 3. Extract dxnt.cab 4. Right click dmusic.inf and select install 5. Profit GL

Now they must publish source code of 7. GL

I think some Wise setups are 16-bit exes, which are not supported on x64 (there is no 16-bit WOW subsystem). Did they work on non-nLited x64 Windows? GL

At first I thought it was this, but when I saw this I'm not so sure any more... And the obvious tricks still apply: restarting client/server, un-mapping and remapping the drive, checking its properties on the server, permissions, temporarily disabling antivirus, if any... GL

Couldn't they improve the core for free and sell the skins to the extremists who want them and are ready to pay for them? (I know it's impossible) B) GL

I've seen some hardware combinations (in this case wireless card and router) that won't work together no matter what, but work fine with other equipment. Maybe the replacement router was also "incompatible" with the card? In my neighborhood, with two different laptops I see two totally different groups of wireless networks. <- Edit: Same channel and everything, of course. Also, turn off all power management for the wireless network card and play with its other (advanced) parameters - there can be many of them, so just type the name of the parameter in Google. GL

I know a Total Commander plugin. Might not be suitable for your purposes (standalone, command line, batch, etc.)? GL

Nothing beats good old manual slashing. This might help. GL

Very often Native Resolution is the largest one you can select (on LCD screens). GL

tchjgangel, if I understood your question, The function in Photo1 is a wizard, to help you KEEP the components which would otherwise be removed in Photo2. Photo1 doesn't do anything, just hides the components in Photo2 from your sight while you work with NLite, so you can not remove them by mistake. The exact mapping (for example, which components would be hidden in Photo2 if you select "Cameras and Camcorders" in Photo1) is known ony to the author of NLite, Nuhi. Many mappings could be determined by experimentation, but I think that would serve no practical purpose. The intention of Photo1 is to protect you from yourself. If you know that you will need that functionality on the computer after the NLited disc is installed, you should check it in Photo1. Many people in the past reported that, for example, if they removed some component in Photo2, some months after the installation of Windows, they couldn't install that Windows component (or driver). And they asked how to add it later (after Windows is installed), but that is not always possible. For example, if you check "Printers..." in Photo1, you are protected from removing Windows printing support (and many built-in Windows printer drivers). If you later (after installation of Windows) connect a printer to your computer, it will be able to install the driver. If you don't check it, and remove some component in Photo2 related to printers, you might not be able to use a printer. Same goes for other components. So, checkmark in Photo1 keeps, checkmark in Photo2 removes. GL