 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Virtual PC / December 2007Windows 98 Crashes in Virtual PC 2007
I have a Virtual PC consisting of Windows 98se which I use to connect to a Novell server and run a DOS application from that server. The Host OS is Windows XP Pro on a Dell laptop. When I boot the Win 98 VPC and ESC at the login screen the VPC seems to work just fine, but when I boot and enter the required login in information for Novell, the VPC will generate WIndows 98 errors or cause Win 98 to hang, or crash resulting in VPC reboot. What could be causing this? I have other laptops from Dell that run Win 98 on VPC just fine. In fact, I have taken their VPC images and used them on the offending PC. In those cases, the VPC will work for a short time and them begin to exibit the same symtoms as before (crashing, rebooting, etc). Footnote: The laptops are connecting through the wireless NIC. We had problems making the connection to Novell using the wireless card as when I would return to the network the server could not be foudn, and then I had to uninstall and reinstall the MS Novell client. Then a resent set Microsoft updates seemed to prevent me from connecting at all to the Novell server through the wireless card. For Win98SE I suggest that you use the virtual machine additions that shipped with VPC 2004, not the ones with 2007. If you don't have VPC 2004 saved somewhere, post back and someone will tell you how to get the additions. >I have a Virtual PC consisting of Windows 98se which I use to connect > to a Novell server and run a DOS application from that server. The [quoted text clipped - 17 lines] > resent set Microsoft updates seemed to prevent me from connecting at > all to the Novell server through the wireless card. > For Win98SE I suggest that you use the virtual machine additions that > shipped with VPC 2004, not the ones with 2007. If you don't have VPC 2004 [quoted text clipped - 24 lines] > > - Show quoted text - Yes, if someone would post a link to the VPC 2004 additions. Or should I be running this application under VPC 2004 and loose any upgraded functionality of VPC 2007? Email me with a working email addy that I can send the 2004 vm additions .iso as a zipped folder attachment. It is 12mb zipped. colinbarharst(remove)@msn.com or c.barnhorst(remove)@comcast.net. >> For Win98SE I suggest that you use the virtual machine additions that >> shipped with VPC 2004, not the ones with 2007. If you don't have VPC [quoted text clipped - 29 lines] > should I be running this application under VPC 2004 and loose any > upgraded functionality of VPC 2007? >Email me with a working email addy that I can send the 2004 vm additions >.iso as a zipped folder attachment. It is 12mb zipped. >colinbarharst(remove)@msn.com or c.barnhorst(remove)@comcast.net. You could just use the link on my website do download: http://www.essjae.com/VPC/VPC2004VMAdditions.zip  SignatureCheers, Steve Jain, Virtual Machine MVP http://vpc.essjae.com/ I do not work for Microsoft. Great. I couldn't remember who had it up. Thanks for jumping in, Steve. >>Email me with a working email addy that I can send the 2004 vm additions >>.iso as a zipped folder attachment. It is 12mb zipped. >>colinbarharst(remove)@msn.com or c.barnhorst(remove)@comcast.net. > > You could just use the link on my website do download: > http://www.essjae.com/VPC/VPC2004VMAdditions.zip Also, it should not be necessary to run the vm under 2004 if what I suspect is true. It may not be the additions but IIRC Win98 is not supported by the 2007 additions so it is worth the try. I don't remember if you have to uninstall the additions in there now but it won't hurt to do so. btw, the msn email address is not a misspelling (long story). >> For Win98SE I suggest that you use the virtual machine additions that >> shipped with VPC 2004, not the ones with 2007. If you don't have VPC [quoted text clipped - 29 lines] > should I be running this application under VPC 2004 and loose any > upgraded functionality of VPC 2007? My win98se works just fine under vpc2007. Not sure if I built it under that or converted it from 2004. > Also, it should not be necessary to run the vm under 2004 if what I suspect > is true. It may not be the additions but IIRC Win98 is not supported by the [quoted text clipped - 36 lines] > > should I be running this application under VPC 2004 and loose any > > upgraded functionality of VPC 2007? His Win98 does also, until he tries to log in to the network. The issue isn't Win98 itself and VPC 2007. My Win98 vm's were created under VPC 2004 as yours probably were. If one doesn't try to update the additions after moving to VPC 2007 the vm should continue to function the same as it did under 2004. > My win98se works just fine under vpc2007. Not sure if I built it under > that [quoted text clipped - 46 lines] >> > should I be running this application under VPC 2004 and loose any >> > upgraded functionality of VPC 2007? >For Win98SE I suggest that you use the virtual machine additions that >shipped with VPC 2004, not the ones with 2007. If you don't have VPC 2004 >saved somewhere, post back and someone will tell you how to get the >additions. That will not work (at least it doesn't work for me). Since upgrading to VPC 2007 my Win 98 SE clients won't synchronise their clocks (worked perfectly fine in VPC 2004 SP1). I tried using the old VM Additions in VPC 2007 but receives the following error on boot... An internal virtual machine error (192) has occurred. The virtual machine will reset now. Anyone knows when/if MS will release updated VM additions to VPC 2007? /CJ Since Win9x/ME is no longer supported starting with VPC 2007, new additions would not make any difference either. >>For Win98SE I suggest that you use the virtual machine additions that >>shipped with VPC 2004, not the ones with 2007. If you don't have VPC 2004 [quoted text clipped - 13 lines] > > /CJ >Since Win9x/ME is no longer supported starting with VPC 2007, new additions >would not make any difference either. Thats a bummer since one of the reason I and many others use VPC is to be able to run older OS and legacy programs! I have a few Windows 9x programs that won't work on Windows XP that I run this way. /CJ >>Since Win9x/ME is no longer supported starting with VPC 2007, new additions >>would not make any difference either. > >Thats a bummer since one of the reason I and many others use VPC is >to be able to run older OS and legacy programs! I have a few Windows >9x programs that won't work on Windows XP that I run this way. Where is the bumming? Win98 runs perfectly well also in VPC2007. If the additions for VPC2004 is what you are after you can download them from Steve Jain's website or get the VPC2004 installer from Microsoft and install that to a different directory from the one suggested by the VPC2004 installer. Yes, you can have both VPC2007 and VPC2004 installed and working side by side! I do this all the time for guests that I must run with VPC2004 because of the RS232 issues. Bo Berglund >Where is the bumming? >Win98 runs perfectly well also in VPC2007. Yes, Win 98 SE runs also in VPC 2007 >but< the time sync between Win XP host -> Win 98 SE guest OS stopped working along the road so saying it works >perfectly< is a stretch IMO. >Yes, you can have both VPC2007 and VPC2004 installed and working side >by side! I do this all the time for guests that I must run with >VPC2004 because of the RS232 issues. I'm aware of that but it's not optimal since VPC 2004 doesn't utilize the Hardware Vitualization available on this new rig. /CJ I have a couple of legacy vm's that had internal virtual machine errors when I brought them up under VPC 2007. It seems to be hit or miss. >>Since Win9x/ME is no longer supported starting with VPC 2007, new >>additions [quoted text clipped - 5 lines] > > /CJ |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.