Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Virtual PC / August 2007



Tip: Looking for answers? Try searching our database.

Server 2003 and VPC problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
dgranger@ball.com - 27 Aug 2007 14:35 GMT
I have been  using VPC 7.0.3 with Windows XP Pro for a while now. I
have just imported a virtual PC using Windows Server 2003 R2 and it
will not boot. I start the machine and get the black screen. I've let
it run all night thinking it may generate an error message, but no
luck. Just the black screen. It does appear that there is some black
type on black screen action going on when it first starts (really
quick flash that makes me think the cursor is advancing), but  it
could be my imagination.

Does anyone know if there is a problem moving the *.vhd and *.vmc
files from MS Virtual PC 2007 to MAC Virtual PC 7? Here's my stats:

   Virtual PC for Mac 7.0 (040819)
   Mac: PowerPC G5 (3.0) dual processor 2GHz
   Memory: 4.5 GB
   OS: Mac OSX 10.3.9 (97W98)
Fred Horvat - 28 Aug 2007 02:34 GMT
Something at the Hardware Abstract Level there is enough differences between
Virtual PC on Windows and the Mac.  I have run into this with XP Pro and
Vista before when importing to the Mac.  You need to install more advanced
Windows from scratch and not import them between platforms.

On 8/27/07 9:35 AM, in article
1188221701.441631.143500@g4g2000hsf.googlegroups.com, "dgranger@ball.com"

> I have been  using VPC 7.0.3 with Windows XP Pro for a while now. I
> have just imported a virtual PC using Windows Server 2003 R2 and it
[quoted text clipped - 12 lines]
>     Memory: 4.5 GB
>     OS: Mac OSX 10.3.9 (97W98)
Steve Jain - 28 Aug 2007 05:27 GMT
>Something at the Hardware Abstract Level there is enough differences between
>Virtual PC on Windows and the Mac.  I have run into this with XP Pro and
>Vista before when importing to the Mac.  You need to install more advanced
>Windows from scratch and not import them between platforms.

No, you should not need to install from scratch.  
The first thing to do is to enable ACPI in the BIOS of the VM in
VPC-Mac.  It is enabled by default on VPC-Win and disabled in VPC-Mac.
This should allow the VM to boot. The rest of the emulated hardware is
very close...other than the CPU which is emulated in the Mac version
and virtualized in the Windows version.
Fred Horvat - 28 Aug 2007 10:58 GMT
I have done this also but Vista for sure will fail to boot.

On 8/28/07 12:27 AM, in article ll87d3d5ivse5e29o3m2r3gsv2dts9lr0t@4ax.com,

>> Something at the Hardware Abstract Level there is enough differences between
>> Virtual PC on Windows and the Mac.  I have run into this with XP Pro and
[quoted text clipped - 7 lines]
> very close...other than the CPU which is emulated in the Mac version
> and virtualized in the Windows version.
dgranger@ball.com - 29 Aug 2007 15:32 GMT
Thanks for that advice, Steve, but what the heck does it mean? I start
up VPC and get a list. There's nothing about ACPI or BIOS in any of
the settings that I can find. Any clue on how to do this?
Steve Jain - 29 Aug 2007 17:11 GMT
>Thanks for that advice, Steve, but what the heck does it mean? I start
>up VPC and get a list. There's nothing about ACPI or BIOS in any of
>the settings that I can find. Any clue on how to do this?

When you start Windows, you need to immediately start pressing the DEL
key, this will get you into VM's BIOS.  From there you will need to
enable ACPI in the BIOS.
Sorry I forgot to mention how to do it.
dgranger@ball.com - 29 Aug 2007 18:12 GMT
Sorry to be such a Mac person, but there's no opportunity for me to
start windows. When I start the VM, I immediately get the black
screen. If I press and hold the delete key as soon as I start the VM,
nothing happens.
dgranger@ball.com - 29 Aug 2007 18:25 GMT
Disregard earlier post. I had to Ctl-Alt-Del at the black screen
stage. I changed the ACPI and the black screen disappeared! It now
gets stuck after the boot screen appears. It checks the files, indexes
and security then restarts. However, once it restarts, it goes right
back into checking the disk again. It's on the third cycle now.
Steve Jain - 29 Aug 2007 19:02 GMT
>Disregard earlier post. I had to Ctl-Alt-Del at the black screen
>stage. I changed the ACPI and the black screen disappeared! It now
>gets stuck after the boot screen appears. It checks the files, indexes
>and security then restarts. However, once it restarts, it goes right
>back into checking the disk again. It's on the third cycle now.

Hmm, that's odd.  Can you try Safe Mode?  Press F8 similar to how you
did DEL, this should give you a menu to boot from.

Otherwise, you could try doing a repair installation via the CD, don't
select the first option to repair, but the second.
Fred Horvat - 30 Aug 2007 01:19 GMT
2003 Server or 2003 Server R2?  I doubt there's a difference but I have both
on the shelf here I could try one out an see what happens.

On 8/29/07 2:02 PM, in article 84dbd31ua5keqg4gi496tt3i1h2blqodd2@4ax.com,

>> Disregard earlier post. I had to Ctl-Alt-Del at the black screen
>> stage. I changed the ACPI and the black screen disappeared! It now
[quoted text clipped - 7 lines]
> Otherwise, you could try doing a repair installation via the CD, don't
> select the first option to repair, but the second.
Fred Horvat - 30 Aug 2007 03:02 GMT
Well I didn't have 2003 R2 at home so I installed 2003 Server and did not
have to change the BIOS for ACPI.  Only for Vista I have I ever had to do
this so far.  

On 8/29/07 2:02 PM, in article 84dbd31ua5keqg4gi496tt3i1h2blqodd2@4ax.com,

>> Disregard earlier post. I had to Ctl-Alt-Del at the black screen
>> stage. I changed the ACPI and the black screen disappeared! It now
[quoted text clipped - 7 lines]
> Otherwise, you could try doing a repair installation via the CD, don't
> select the first option to repair, but the second.
 
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.