Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    United States

Everything posted by scott14

  1. a) do the registry edit newsposter explained in this other thread: http://www.msfn.org/board/index.php?showtopic=98421 B) As Nuhi says in that other thread, turn on these 2 services:: Secondary Logon Shell Services and also turn on these 3 services: Fast user switching Remote Procedure Call (RPC} Terminal Services c) Start / Control Panel / User accounts / under the area "Pick a task" click on "Change the way users log onn or off" and on the next screen check the box for "Use fast user switching."
  2. antinouskalisto, Thank you for your comments. Well at least it's good to hear that I'm not the only person with this problem. My HDDs are not in raid array. One of the 3 is an "Acronis secure zone" so Windoes can't see it. I think that's why only 2 of my 3 HDDs show up as removable devices in the Safely Remove Hardware icon. THat's also good news. I've been woried that other people using this computer would accidentally "remove" the hard drives when they took out their thumb drives. From what you say I won't worry any more.
  3. Now I've got a real nice new nLite installation, except for 1 thing that I don't know how to fix: Normally your "Safely Remove Hardware" tray icon turns on when you plug in a USB device. The problem is, in my new Winlite installation, the "Safely Remove Hardware" tray icon stays on 100% of the time, and the hardware which it shows are 2 of my 3 HARD DRIVES! Does anybody have ideas on how to disassociate my HDDs from the Windows XP "Safely Remove Hardware" feature? 4 people use this desktop computer, with lots of thumb drive connections coming and going all the time, so I fear someone will mistakenly shut off a HDD when using "Safely Remove Hardware" to remove their USB flash drive. Your thoughts / suggestions on how to fix this will be appreciated. It'd be much better to still have the "Safely Remove Hardware" feature remain useable for the thumb drives, instead of totally disabling it (which I don't know how to do anyway). Thank you.
  4. Really, don't you think it's better to appreciate what Nuhi gave us all free, only humbly suggesting a voluntary donation? That's especially true when you remember the huge number of hours invested into programming nLite, and the complicated job it performs with just a few easy clicks! I think we'll all agree nLite is a wonderful tool, and it has helped us a LOT, so it's really better to appreciate it. And he supports it and continually improves it little by little. I think Nuhi understands Windows better than a lot of Microsoft software engineers, and we get the benefit of that. In anything in this life, "perfection" is always a goal on the far horizon. "Perfection" is never truly achieved in anything . . .we never finally get there, to perfection, in anything.
  5. Thank you both. Problem now fixed. I appreciate the help each of you gave me. Scott
  6. (Normally I'd never cross post on a forum, but I didn't get a single reply in the Windows Unattended forum after several days, so I'm reposting this here.) I'm unable to get Fast User Switching service to work after unattended Windows XP Pro SP2 installations with nLite v. 1.3.5. Even after manually going into Windows XP's Services and setting Fast User Switching, and the other 2 things which it depends upon: Remote Procedure Call and Terminal Services, all to Automatic and all Started, the Fast User Switching still doesn't work. Fast User Switching service works A. OK after an ordinary, non-slimmed down, non-nLite installation. Does anybody have thoughts on how to get Fast User Switching to work for an nLite installation (WinXPProSP2)? 4 users share the main desktop computer here and that feature is used a lot, we need it. Thank you.
  7. scott14

    Disabled service

    Yes, it helped me. Thank you for solving this issue. I've been having exactly the same problem. When I start a service manually that had been disabled during nLite, it reverts back to disabled status after reboot. In my case, unlike you, I don't have the 3 nLite files nor a RunOnce key at HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce. However, your solution gives me a good start toward fixing this.
  8. Make sure to click the "Make ISO" button , not the "Next" button.
  9. At nLite's "Task Selection" screen, (3rd screen after the start) click the buttons for the things you want to change this time, so the green light shows beside the buttons. Be sure the Bootable ISO button at bottom of list has a green light. Click to make the light red beside the items you want to leave alone, and they will be same as last time. If you just want to look at the entries you made last time, for the buttons on the Task Selection" screen (Hotfixes, Addons and Update Packs, Components, Unattended, Options, Tweaks) you can click their buttons to green and look at them again this time through, and nLite will still keep same info as last time. Like I said before, there's one exception (at least in my case). On the "Task Selection" screen, if you click the Drivers button to make its light green, nLight deletes all the drivers so you have to load them all again. So if you loaded your drivers last time, don't look at the Drivers page again next time.
  10. Well I'm still a nooby at nLite, but I had the same trouble as you. I wasted about 12 CD-ROMs that would not boot. What finally worked for me was to burn the CD-ROM from nLite instead of frm Nero Burning ROM, and these settings: on nLite's "Bootable ISO" screen, select Mode=Direct Burn, ISO Engine=Mkisofs, Boot Sector=Default Burn Speed=Slowest that you can set I think you can run it again if on the nLite "Presets" screen, you check the box for Load 'Last Session' on startup. Also, in my own case, on nLite's Task Selection page, if I don't select Drivers then nLite still keeps all the same drivers from last time. However, if I do select the Drivers page, then nLite deletes all the drivers from last time and I have to reload them all again. I don't know if that will be the same in your experience. Good luck!
  11. It's quite an honor that YOU replied to my question. Thank you! And, now my confusion about this point is all gone and I understand.
  12. Oh, now I see what you're thinking. I was thinking that for SFC /scannow I'd need to put the original Windows XP disk from Microsoft into the CD-ROM tray. You're saying that, no, you'd put the WinLite disk in.
  13. If you were to run the command sfc /scannow, would that just reinstall the Windows junk that nLite removed?
  14. Try right-click on the XP_Source folder remove checkmark from readonly and then apply it to all subfolders and files... Also check that you have NTFS Write and Modify permission on that folder (Security tab in XP Pro, if you have XP Home then ignore this sentence). This will be done automatically in the next version. n7Epsilon, Thank you.
  15. 32-bit WinXPSP2 I got this same error many times. I do not use your WMP Slipstreamer by itself. nLite v1.3.0.4 calls your WMP Slipstreamer v. 070 when nLite runs. After nLite, the WMP is v.9. The error message tells me to post the bug report. Here it is as requested: QUOTE System.UnauthorizedAccessException: Access to the path 'C:\Slipstream\XP_Source\i386\asferror.dl_' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.Delete(String path) at WMP11Slipstreamer.Backend.MergeFolders() at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings) Unfortunately, the error occurred during the critical process of overwriting files in the "i386" folder. This source can no longer be used reliably, please use a fresh new source for subsequent windows setup installations and modifications. Temporary folder: "C:\Slipstream\XP_Source\i386\wmp11temp" We apologize for any inconvenience. Please report this bug. END QUOTE This is my SVCPACK as copied from my folder at C:\Slipstream\XP_Source\I386\wmp11temp\SVCPACK
  16. scott14

    Advice request

    neo & zikozoko, Thank you both for your advice.
  17. scott14

    Advice request

    I'm still an nLite noobie. I have an nLite .iso burned onto a CD-ROM. When I mount the nLite .iso with Microsoft Virtual Machine 2007, it boots and completely installs WindowsXPSP2 and addons with no errors. It works beautifully in the VM. When I set bios to boot from the same CD-ROM for real installation, it does not boot. There is also another place outside of bios to select the boot device, and I also set that to boot from CD-ROM too. Summary: Works perfectly in VM, does not work for real. If anybody have a suggestion to straighten me out and get this to work, I will appreciate it. mobo=DFI LanParty nF4.
  18. The Winlite ISO works beautifully in MS Virtual PC 2007. After setting the CD-ROM as 1st boot device in bios, all it does is say "Error loading OS" Does anyone have ideas how to solve this? It's a big problem to me, but maybe only a little problem to some of you who have more experience. Thank you.
  19. Erik, Why spend all that money on Vista when your XP rig is running well? I'm sticking with XP for awhile. Someday instead of Vista I may try Suse Linux instead.
  20. The purpose of this post is to try & help the next guy who has this same problem. SOLVED: Based on bonestonne''s post I disconnected the DVD drive. The BSOD error then immediately changed from "atapi.sys" to "sptd.sys" which relates to Daemon Tools. Uninstalled Daemon Tools and the crashing instantly ceased. Where as previously I couldn't run more than 10 minutes w/o a BSOD, after uninstalling Daemon Tools there has not been a crash for over 24 hrs. So bonestonne was right, it was an optical drive...the virtual optical drive set up by Daemon Tools. Must be a driver conflict with something else, I'm still tracing the conflict down.
  21. Post removed. I finally got it to work. THANK YOU FOR nLITE, NUHI. YOUR WORK IS EXCELLENT!
  22. Thanks everybody. The full memory dump file, after compression into a .rar, is 487 MB. I can't keep it alive long enough to ftp upload the huge file. However, I really appreciate all the comments intended to help. I plan to start stripping out components, and see what makes a difference, starting off with the DVD burners. THANK YOU ALL.
  23. OK, I will make a new memory dump and upload it again. The previous one (the one you were unable to see) is zipped with 7-Zip. On the new one I'll zip it with .rar Thank you both very much for your willingness to comment.
  24. nitroshift, Thank you for your reply! O.K., the full memory dump created with Debugging Tools for Windows is on the web at: UPDATE: unable to keep the computer alive long enough to ftp upload the FullMemoryDump.rar file< which is 498,948 KB in size. Thank you anyway.

  • Create New...