Main > Main Forum

Ipac 4 sticking on startup?

<< < (2/2)

Peja:
Not sure what is going on with my computer now but it isn't playing nice right now.  I tried running the usb cables individually and now my device manager keeps refreshing and playing the tone it does whenever you connect a new peripheral. 

It seems to be just the U360's that are causing it.  My ipac4 and trackball don't seem to do it. 

Also, my ipac 4 is still sticking when running it direct.  Here is what the start bar will look like when it happens.  It isn't every time.....just random and about 50% of the time.  It happens if the u360s are connected and if they aren't. 




And on my Win 7 startup.  I get the boot manager about 75% of the time.  Except there is no countdown clock.  So I have to hit enter every time.  Kind of sucks to have a keyboard connected at all times.  Changing the time in msconfig doesn't do anything either.  It's this screen except for its Win7 not Vista.  And there is only one option in there.....Win7 since that is the only OS I have had installed on that drive.





I don't want to do a clean format and install but will if that is what I need to do.  It just sucks reinstalling all of the emulators, led blinky, hypserspin, etc etc.  If there is any easy way to do that, I would be open to it but not sure if there is.

Thanks for any other help you can give me.

Peaj


Peja:
Update:

Not sure if it is completely fixed yet but I ended up seeing an unknown device in the device manager called coprocessor.  A little google search showed me this is related to the nvidia chipset driver.  I found the driver, installed it, and the unknown device went away. 

I then plugged in all of my usb devices and none of them caused the device manager to keep refreshing.  I also restarted my computer 5 times with the the ipac working just fine.  No repeat characters.  My boot manager screen also didn't pop up. 

I will have to restart about 10 more times though to really get an idea if it is fixed.  Sometimes it does it and sometimes it doesn't. 

Hopefully all of this is due to a simple chipset driver becoming uninstalled somehow. 

Thanks,
Peja

Navigation

[0] Message Index

[*] Previous page

Go to full version