VCC

Member
  • Content count

    112
  • Joined

  • Last visited

Community Reputation

0 Neutral

About VCC

  • Rank
    Member

Contact Methods

  • MSN
    rjlangley@yahoo.com
  • Website URL
    http://www.venturacc.com
  • Yahoo
    rjlangley
  1. Actually, if you're getting to where you can see MUP.SYS, then the problem lies with the service that is trying to load after MUP.SYS and that will depend on the the Start order of services on your machine. 0 = boot, 1 - system, 2 = automatic (which is going to be the service start type you may want to focus on due to where your system is crashing; though it could be a 1 that is loading directly after Mup.sys and just before the 2s.) I typically focus on Video drivers when this happens, they (and the lack of properly loaded video drivers) are notorious for causing this particulas crash. To find get to where you can adjust the Start type of a service, I suggest having a BartPE disk with RegeditPE on the disk. Or you can also try to use Shift+F10 in setup before it restarts and run helpful commands there, go into control panels, etc. You should be able to find more information on why it is stopping at MUP.SYS using google search. With some research, you should be able to get through it. I have, quite a few times.
  2. Suggestion: Search = "Registry Tweaks" or from what you even typed "Copy to" or "Move to" And here is the gift (Credit, in my find, goes to gui_m in post "http://www.msfn.org/board/Registry-Tweaks-Part-1-t21814.html"): ;-----------------------------------------------------------CONTEXT MENU HANDLERS---------------------------------------------------- ;Right-Click Copy-To [HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers] [HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\Copy To] @="{C2FBB630-2971-11D1-A18C-00C04FD75D13}" ;Right-Click Move-To [HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\Move To] @="{C2FBB631-2971-11D1-A18C-00C04FD75D13}" ;This adds the "Open Command Window Here" on the right-click menu for folders [HKEY_CLASSES_ROOT\Directory\shell\cmd] @="Open Command Window Here" [HKEY_CLASSES_ROOT\Directory\shell\cmd\command] @="cmd.exe /k \"cd %L\""
  3. Registry Entry for My Computer: HKEY_CLASSES_ROOT\CLSID\ KEY: {20D04FE0-3AEA-1069-A2D8-08002B30309D} "My Computer" name: String "LocalizedString" - @%SystemRoot%\system32\SHELL32.dll,-9216
  4. This isn't going to be a completely detailed, instruction based answer at the moment. But check out PowerPacker. It has the ability to not only make a multiboot disk, but to integrate other directories (like the ones on the 2nd disk) onto your install disk. I'm sure if you go to the forum for Powerpacker the creator, or someone there, will be happy to assist with how to do it with the PowerPacker.
  5. Yes - with RVM Integrator and WPI plugin (plugin installed from a menu choice in the Integrator) there are other ways with the Integrator, but this way is the latest.
  6. Glad you got it. If you haven't already, check out the RVM Integrator for integrating updates.
  7. Because integrating MassStorage drivers are more difficult than just copying the files to a location. Consult the Driverpacks forum to learn more. If you need to integrate them yourself, you're going to have to learn a couple of things about integrating MassStorage drivers. Oh, and the best place to learn is the Driverpacks forum.
  8. Glad to hear it. Weird though. I've heard of others using CD-RW and it working okay. I just choose to use CD-R though myself. Headache over now, huh
  9. I just reviewed my IM history of the conversation I had with my cousin about this who is the Dev. for RVM Integrator & the PowerPacker. We were bouncing ideas off each other trying to figure it out until I finally decided to hand it over to the company we buy computers from, since I don't have the extra hardware at work to swap out parts usually. I was focusing my attention mainly on software and testing hardware, but none of the hardware tests complained of the CPU. I'll add that this computer was experiencing errors in Windows beforehand about running low on virtual memory. It turned out to be the CPU was just bad enough that the computer was sometimes usable. When I tried reloading Windows I would get different errors at different times, but it started with the T-39 error repetitively. Once the processor was changed out Windows loaded with no further problems. Keep in mind that I had loaded Windows XP on this computer twice previously, the first was when we received the computer and the second was after the user was complaining of the low virtual memory errors and I couldn't figure out for the life of me what was causing it (I have experience in fixing these errors otherwise). The computer vendor we use had a very tough time with it also, it took a few days for them to decide to swap out the processor (Intel Core 2 DUO running on an Intel Desktop board) Check your memory first to make sure you're not having memory problems. SXS.DLL is used to verify the Manifest of the system files to make sure what is copied over to the hard disk is copied correctly. A bad CD/DVD drive I suppose could also cause these errors, but you'd probably run into problem just booting up to the disk in that case.
  10. Post what you are using to create your disks. I've run into this, I'm trying to remember what the deal was. All I can think of at the moment is Bad Disk. But I'm still trying to be sure of that. I'm not having that problem anymore.
  11. OH, Virtual Machines, okay. Is it VMWare, never had a problem with that one. BTW, Driverpacks would do no good in a virtual machine.
  12. Sounds like a driver issue. Are you using the Driverpacks? If not, might be a good place to start. Not that you need to, but they are great if you deal with many different configurations. If it is just the laptop. Which laptop is it (Model)? I had a problem before with an HP Compaq 6710b and found that it was the mass storage driver.
  13. Maybe a limitation with the video. What is the video settings looking like? What is your method of integration, my suggestion would be with RVM Integrator.
  14. Dude, if you're having problems with the RVM Integrator, you might be doing something wrong. Mixed with the PowerPacker and DriverPacks you should have great results. Though, I have had some issues in the path with one or the other I know the RVM Integrator is solid at the moment (I use it all the time), as is PowerPacker these days. DriverPacks are going through some really cool improvements and should give great results also.
  15. RVM Integrator + WPI + Powerpacker = Unattended/Integrated Windows XP disk with programs/updates, etc.