andreyvul Posted December 28, 2009 Author Share Posted December 28, 2009 (edited) andreyvul, you never answered my questions from an older reply, such as where your source came from. Knowing little at this time I would be more suspicious of the AMDAway driver. What purpose does it serve? Please post a link to where you DLed all the ATI and the AMDAway drivers. At this time I think maybe the best starting point is to remove all but the text mode drivers and see if the mouse works. Enjoy, John.The source is from MSDN. I have a MSDN subscription and downloaded it from there.AMDAway is a driver for Cool'n'Quiet support.The drivers were downloaded from MSI's download page for the 785GT-E45 motherboard. Edited December 28, 2009 by andreyvul Link to comment Share on other sites More sharing options...
johnhc Posted December 29, 2009 Share Posted December 29, 2009 andreyvul, AMDAway is not a Cool'n'Quiet driver. Here is what MSI DL page says for 785GTM-E45 MB.This INF file removes the unresolved hardware detection (YELLOW BANG! associated with devices that do not have the proper driver installed) only.Ver. 1.0.1.0I don't think I would want this on my system anyway. I would want to know about missing drivers. BTW, Cool'n'Quiet is not really a driver but just an application. Please run the experiment I suggested and let us hear the results and please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John. Link to comment Share on other sites More sharing options...
andreyvul Posted December 29, 2009 Author Share Posted December 29, 2009 Halfway through 'Installing Devices', USB dies again. It wasn't the drivers.Also, thanks for the typo fix. It _was_ GTM, I just missed the M.Last_Session.ini Link to comment Share on other sites More sharing options...
johnhc Posted December 29, 2009 Share Posted December 29, 2009 andreyvul, OK, thanks. I think now you should try Kurt_Aust's suggestion in another thread where lots of stuff was removed/tweaked. Run nLite (starting with a fresh copy of CD files/folders), remove nothing and tweak nothing. You need to permanently remove "Explorer-Launch folder windows in a separate process". It exposes a Windows bug, but is not your problem. I would warn against "CDPromptRemove" in options. This can cause Setup to start over and over. I am not familiar with "DisableFreereq" and "AdvTweaks" and can't find them in my Options Task (I am running x64). What are they and what do they do? For your test run, they should be removed. What is the ERSvc service you have disabled? Please let us hear the results. Good luck, John. Link to comment Share on other sites More sharing options...
andreyvul Posted December 29, 2009 Author Share Posted December 29, 2009 andreyvul, OK, thanks. I think now you should try Kurt_Aust's suggestion in another thread where lots of stuff was removed/tweaked. Run nLite (starting with a fresh copy of CD files/folders), remove nothing and tweak nothing. You need to permanently remove "Explorer-Launch folder windows in a separate process". It exposes a Windows bug, but is not your problem.So basically, stock XP with F6-floppy drivers merged?I am not familiar with "DisableFreereq" and "AdvTweaks" and can't find them in my Options Task (I am running x64). What are they and what do they do?Disable Free Space requirement. It's in the Setup options task.What is the ERSvc service you have disabled?Error Reporting. Link to comment Share on other sites More sharing options...
johnhc Posted December 29, 2009 Share Posted December 29, 2009 andreyvul, yes, basically I think you need to get down to the fundament and something that works. Hope you can give it a try. Enjoy, John. Link to comment Share on other sites More sharing options...
andreyvul Posted December 30, 2009 Author Share Posted December 30, 2009 (edited) I facepalmed so hard right now.The mouse wasn't working because it was connected to a USB hub, not directly to a USB root port. Same thing happened with a USB keyboard in Linux.After setup, same thing - directly to motherboard, mouse works; via hub, mouse doesn't work.I have no idea why this is happening. Any suggestions?And it's not a hardware problem, since I pop in a Knoppix livecd and everything works. Edited December 30, 2009 by andreyvul Link to comment Share on other sites More sharing options...
johnhc Posted December 31, 2009 Share Posted December 31, 2009 andreyvul, so you are saying that it would have worked all along if plugged directly into a USB port? I would check with the mouse vendor tech support. Have you done some Googling? Good luck, John. Link to comment Share on other sites More sharing options...
andreyvul Posted January 1, 2010 Author Share Posted January 1, 2010 andreyvul, so you are saying that it would have worked all along if plugged directly into a USB port? I would check with the mouse vendor tech support. Have you done some Googling? Good luck, John.The it-works-in-Linux argument is perfectly valid here. But a Windows bug is a Windows bug - you can't just recompile the kernel.Also, happy new year! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now