Jump to content

Windows reinstall: mouse freeze


Recommended Posts

Posted

Hi Guys

I just spent the weekend (!) setting up various nLited xp discs.

1) XP Pro OEM

2) XP Home OEM

3) XP Pro VLK for work...

The first 4 (!) times I tried to create discs with all my (time-consuming) tweaks and unattended goodies added. Great, I thought.

The result

I would get the mouse totally lose input at the bit where it asks you that Windows is going to change the resolution and asks you to press OK (sorry, the exact wording escapes me). On all discs where I selected all my tweaks (OEM Pro, OEM Home and VLK). It's like the mouse isn't connected at all. A reboot and retry is all you can try, and that still doesn't fix it.

By-the-book

For all operations, I started from BARE, original XP discs, not previously nLited stuff.

The Pro OEM and Home OEM discs were SP1 discs integrating SP2 and RyanVM 2.1.3 and a few drivers.

Same stuff was done with the VLK disc, though it had no SP on there to start with.

Background

The last disc I made (just then) was a success, but only because I decided to troubleshoot and not select the 'unattended' stuff in nLite and not make any changes to the default Windows interface settings (show hidden files, etc, etc) or disable any services. It worked fine; no total loss of mouse input at that point and things ran normally - just like it should.

So, my question is, just so I can nail things down is:

Which one of my settings/tweaks in nLite could have created this problem? All I did was make quite a few cosmetic changes to Windows (disabling IE shortcuts, showing hidden files, etc, etc - sorry but I didn't write them all down, but I can replicate exactly what I did easily by having the choices in front of me). I also distinctly remember disabling the following services:

Automatic Updates

Background Intelligent Transfer Service

Error Reporting Service

IMAPI CD-burning COM service

Windows Time

Basically, not making any unattended tweaks or Windows interface tweaks (apart from the raw sp2 integration and Ryan VM 2.1.3 integration) stops this problem. But what caused the problem to start with? Or do I have to go down the long, hard road of trying each thing one-by-one? :no::realmad::ph34r::D

Appreciate any help/insight!


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...