![]() ![]() My searches did not reveal any good articles on that specific subject. Since I cannot get past the invisible sign-on screen, I am not sure how to attempt "a remote registry edit" on the virtual machine that is running. In the article it appeared that in order to fix the registry on the affected computer, you first had to get past the invisible screen. So in the blank screen I have tried every combination of entering the password and clicking on different areas of the screen to see if I can get past the invisible sign-on screen.but no luck. The physical machine that the vhd was created from had two login users displayed on the sign-on screen and I attempted to follow the steps described in the recommended Microsoft article. ![]() Regarding the Virtual PC attempt - since Virtual PC on Windows 7 enables XP pro legacy applications to be a Short Cut right on the Windows 7 desktop (my next step), I am currently focusing on getting past this blank screen in Virtual PC first. For now I am going to focus on the Virtual PC first (see below). I need to figure out how to freeze the BSOD and capture the error code to determine the next step of troubleshooting (VMware just keeps rebooting and the BSOD just flashes for a second). As carefully as I can follow the instructions - I get the Blue Screen of Death when VMware attempts to start the virtual machine on the WIndows 7 host 64bit with SATA drives. Regarding the VMware attempt - the physical machine used to create the virtual machine was an OEM computer with XP pro 32 bit and old IDE drives. Thank you for the quick response and right after your comments were posted I attempted to follow both the VMware workaround and the Virtual PC article from Microsoft but I did not want to post back my unsuccesful results until I could complete more comprehensive tests. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |