I believe at the time, I chose the Windows_Server_2003 module for 64-bit XP 
because it seemed to be the closest match, and we aren't running any Windows 
Server 2003 here, so I knew it would be safe to place 64-bit drivers in there. 
And I wasn't smart enough to write my own module :)

I haven't created a vmware-based 64-bit XP image, only bare metal. I wanted the 
64-bit version so we could take advantage of all the memory on the bare metal 

Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB #3420, ITS Manning, Rm 2509

-----Original Message-----
From: Andy Kurth [mailto:andy_ku...@ncsu.edu] 
Sent: Tuesday, May 11, 2010 10:15 AM
To: vcl-dev@incubator.apache.org
Subject: Re: windows 64 bit support

Good info Mike.  Hopefully the next release will make this a little less 

> - Install Windows-64 hotfix for Sysnative path to work.

Yes.  You'll need this:

If you can't run the following command on a 64-bit installation then things 
won't work:
dir C:\Windows\Sysnative

> - Create symlinks for shutdown.exe, defrag.exe in system32 folder.

The code will need to be checked for these and all other calls to .exe's in 
System32.  This won't be a requirement in the next release.

> - Use the Windows_Server_2003 module in the OS table for winxp64 OS.

Was this required so VMware would set the guestOS setting in the .vmx file to 
something that worked for 64-bit, or was there another reason?

> - Replace Sysprep and Broadcom drivers under
>   /usr/local/vcl/tools/Windows_Server_2003 with 64-bit versions. 

We'll need to design the drivers directories out a little better.  As of now, 
the tools/Windows<_version>/drivers directories are copied during image capture 
and there are no provisions for different architectures.  If you want to run 
both 32 and 64-bit versions of the same Windows OS, the drivers for both will 
copied.  This could cause conflicts if Sysprep doesn't choose the correct 

Also add 64-bit version of spdrvscn.exe.

The requirement for spdrvscn.exe has been removed in the latest code but you'll 
need the correct version of this utility for 2.1 and earlier.  This utility 
scans the driver .inf files and populates the DevicePath registry key with all 
of the paths it finds.  The vcld Perl code now does this.  The new code also 
automatically populates the mass storage section of sysprep.inf will the paths 
to all of the storage .inf's it finds.


Reply via email to