No. Actually I don't, because I'm not suspecting a driver.
Jay's computer runs fine after Windows is loaded and he gets past this "annoying blank screen". So if there was a bad driver, wouldn't it still be causing difficulties with the Operating System and applications?
I'm still suspecting a "file association" of the type that you've already repaired 2 out of 3 for Jay with your recommended "Regfixes"
Then click COM File Association Fix ( downloads a ZIP file that contains xp_com_fix.reg )
Then click SCR File Association Fix ( downloads a ZIP file that contains xp_scr_fix.reg )
We still have the executable .pif to reintall or repair. I think in this situation, .pif file commands may be those associated with MS DOS commands prior to loading of Windows. I don't "know" that, but that's what I'm thinking.
What do you think about having Jay go take a look at the Dword Value data for these entries, as per my earlier PM to you.
Mind you, I'm just suggesting he go take a look. Not make any changes. But if the Dword Value data is 0 or "no value data entered" then we will probably continue to be dead in the water.
Alternatively, we could get the same information if you recommended to him to use HJT misc tools to generate another StartUp log.
I'm gonna make a guess that in the two instances that you've "fixed",
that the Dword Value data will appear as %1% for .com and %1% /S for .scr
And I'm gonna make a guess that in the one instance that we haven't been able to find a .reg fix for, that the Dword Value data will be blank or "no value data entered"
I'd also like to consider "replacing" the regedit.exe in C:\Windows and the other appropriate locations with original values from the C:\Windows\i386 folder.
Jay, Please understand that this is just a conversation and that I am not ready to make such a recommendation to you as yet.
Two or three heads are indeed better than one, as you previously mentioned. Thanks for understanding.
Best Regards
Edited by dough, 09 August 2006 - 10:21 PM.