Gregoverhead
I do a lot of commercial work with Virtualbox so if you have any issues
then yell out.
Some key points are:
1. Run GUI Virtual Hosts as Headless to minimize memory and processor
2. Use Remote Desktop to access the Headless VM's
3. If you install XP or 2000 in a VM make sure its just the OS + Service Packs and the required Wildcat! files don't clutter it up with other apps.
4. Whilst you can use VBoxManage to expand Virtual Disks its always better with Windows O/S to have a larger partition from the beginning say 60GB+ rather than the default 10 to 20GB
5. I am running Windows XP with Wins in a VM on my Fedora Linux Box to if you wanted to go the Linux route that will also work in terms of the underlying comms.
Mike
On 10/28/2012 3:49 AM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:
Hello Mike
The system is running fine, for that matter so good I hate to say anything.
Two questions though.
I see on google their is many ways to run headless, what way would you suggest? I'm running Win XP on top of Win2008?
Also, would you suggest running PX Express on Win 2008 or XP? I read were Fred installed it on the 64 bit OS but used a share CD drive off of a 32
bit OS.
What would you suggest?
Thanks for your time
Greg
apps.Greg
I do a lot of commercial work with Virtualbox so if you have any issues then yell out.
Some key points are:
1. Run GUI Virtual Hosts as Headless to minimize memory and processoroverhead
2. Use Remote Desktop to access the Headless VM's
3. If you install XP or 2000 in a VM make sure its just the OS + Service Packs and the required Wildcat! files don't clutter it up with other
better4. Whilst you can use VBoxManage to expand Virtual Disks its always
ifwith Windows O/S to have a larger partition from the beginning say 60GB+ rather than the default 10 to 20GB
5. I am running Windows XP with Wins in a VM on my Fedora Linux Box to
you wanted to go the Linux route that will also work in terms of the underlying comms.
Mike
GregXP VM
While your testing to see how things run I would keep it very simple!:
1. Make sure you can remote desktop from Windows 2008 to the Windows
2. Close down the XP VMsuccessfully
3. Create a basic batch file like
-- START XPVM.bat EXAMPLE:
cd "c:\program files\oracle\virtualbox"
vboxmanage startvm "Windows XP" --type headless
-----
Remember the VM Name is case sensitive so whatever you named it must be
what follows STARTVM
Run the batch file at the Command Prompt and you should see a
started message.experiment
If after a period of testing it all seems to run ok then you can
with more advanced HEADless approaches.Windows8+
I would try running PX in Windows XP so that if you would move to
you want need to solve new problems with each new Host OS.
Mike
Hello Mike
While I was waiting for a reply I downloaded and am right now trying
(V BOX HEADLESS TRAY) neet little program.
I'll try PX on WinXP then!
I do notice the 16 bit doors being a little laggy but maybe that will change some after I move this setup over to server with more power.
I have tweaked everything I can think of in XP that I can think of.
Thanks for all the help so far, laughing I may have more though.
Greg
On 11/3/2012 7:45 PM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:
Greg
While your testing to see how things run I would keep it very simple!:
1. Make sure you can remote desktop from Windows 2008 to the WindowsXP VM
2. Close down the XP VM
3. Create a basic batch file like
-- START XPVM.bat EXAMPLE:
cd "c:\program files\oracle\virtualbox"
vboxmanage startvm "Windows XP" --type headless
-----
Remember the VM Name is case sensitive so whatever you named it must be what follows STARTVM
Run the batch file at the Command Prompt and you should see asuccessfully
started message.
If after a period of testing it all seems to run ok then you canexperiment
with more advanced HEADless approaches.
I would try running PX in Windows XP so that if you would move toWindows8+
you want need to solve new problems with each new Host OS.
Mike
You can run VB on a single core with 4G Memory but put simply thatisn't the target platform
The assumption is that you will be running on a server (not desktop)with
max RAM and at least a Quad Core+. A dual core will work but youwould be
limited to a very small number of Virtual Machines even in headlessmode.
You also want to make sure your Host OS is using a physically separate Network Interface Card to the Virtual Machines. When you startsharing the
host NIC with the VM's it slows things down and potentially causes odd Windows TCP Stack problems.to a
When you have the server hardware in place you can then fine tune the Settings for each of your VM's to reduce overhead and lag.
I suggest you experiment as much as possible before moving everything
production environment.
Mike
Morning Mike
Right now it is on a single core xeon e server IBM but I will be moving it to a Dell Quad core poweredge server with 16 gigs of ram so I should be good to go there.
The last thing I did last night was move the VM to another nic card so I will be testing that today and tomorrow.
Thanks for the tips though, I fell a little better knowing I'm going in
the right direction.
Greg
You can run VB on a single core with 4G Memory but put simply thatisn't the target platform
The assumption is that you will be running on a server (not desktop)with
max RAM and at least a Quad Core+. A dual core will work but youwould be
limited to a very small number of Virtual Machines even in headlessmode.
You also want to make sure your Host OS is using a physically separate Network Interface Card to the Virtual Machines. When you startsharing the
host NIC with the VM's it slows things down and potentially causes odd Windows TCP Stack problems.
When you have the server hardware in place you can then fine tune the Settings for each of your VM's to reduce overhead and lag.
I suggest you experiment as much as possible before moving everythingto a
production environment.
Mike
Gregor
Your definitely on the right path.
I think for anyone with a requirement to run legacy Operating Systems
8/16 bit application it is the best course to follow rather thanlooking
for hacks or emulation software.in
Time permitting it would be worth you documenting your experience as it could assist other legacy door users and perhaps should be a tech note
Hectors knowledge base.moving it
Mike
On 11/5/2012 3:55 AM, GREG YOUNGBLOOD wrote to MICHAEL PURDY:
Morning Mike
Right now it is on a single core xeon e server IBM but I will be
should beto a Dell Quad core poweredge server with 16 gigs of ram so I
so Igood to go there.
The last thing I did last night was move the VM to another nic card
going inwill be testing that today and tomorrow.
Thanks for the tips though, I fell a little better knowing I'm
thatthe right direction.
Greg
You can run VB on a single core with 4G Memory but put simply
desktop)isn't the target platform
The assumption is that you will be running on a server (not
youwith
max RAM and at least a Quad Core+. A dual core will work but
headlesswould be
limited to a very small number of Virtual Machines even in
separatemode.
You also want to make sure your Host OS is using a physically
causes oddNetwork Interface Card to the Virtual Machines. When you startsharing the
host NIC with the VM's it slows things down and potentially
tune theWindows TCP Stack problems.
When you have the server hardware in place you can then fine
everythingSettings for each of your VM's to reduce overhead and lag.
I suggest you experiment as much as possible before moving
to a
production environment.
Mike
Gregit
Your definitely on the right path.
I think for anyone with a requirement to run legacy Operating Systems or 8/16 bit application it is the best course to follow rather than looking
for hacks or emulation software.
Time permitting it would be worth you documenting your experience as it could assist other legacy door users and perhaps should be a tech note in Hectors knowledge base.
Mike
On 11/5/2012 3:55 AM, GREG YOUNGBLOOD wrote to MICHAEL PURDY:
Morning Mike
Right now it is on a single core xeon e server IBM but I will be moving
separateto a Dell Quad core poweredge server with 16 gigs of ram so I should be good to go there.
The last thing I did last night was move the VM to another nic card so I will be testing that today and tomorrow.
Thanks for the tips though, I fell a little better knowing I'm going in the right direction.
Greg
You can run VB on a single core with 4G Memory but put simply thatisn't the target platform
The assumption is that you will be running on a server (not desktop)with
max RAM and at least a Quad Core+. A dual core will work but youwould be
limited to a very small number of Virtual Machines even in headlessmode.
You also want to make sure your Host OS is using a physically
oddNetwork Interface Card to the Virtual Machines. When you startsharing the
host NIC with the VM's it slows things down and potentially causes
--- Platinum Xpress/Win/WINServer v3.1Windows TCP Stack problems.
When you have the server hardware in place you can then fine tune the Settings for each of your VM's to reduce overhead and lag.
I suggest you experiment as much as possible before moving everythingto a
production environment.
Mike
On 10/28/2012 3:49 AM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:
Hello Mikeanything.
The system is running fine, for that matter so good I hate to say
Two questions though.were
I see on google their is many ways to run headless, what way would you suggest? I'm running Win XP on top of Win2008?
Also, would you suggest running PX Express on Win 2008 or XP? I read
Fred installed it on the 64 bit OS but used a share CD drive off of a 32
bit OS.
What would you suggest?
Thanks for your time
Greg
issuesGreg
I do a lot of commercial work with Virtualbox so if you have any
Servicethen yell out.
Some key points are:
1. Run GUI Virtual Hosts as Headless to minimize memory and processoroverhead
2. Use Remote Desktop to access the Headless VM's
3. If you install XP or 2000 in a VM make sure its just the OS +
apps.Packs and the required Wildcat! files don't clutter it up with other
better4. Whilst you can use VBoxManage to expand Virtual Disks its always
60GB+with Windows O/S to have a larger partition from the beginning say
to ifrather than the default 10 to 20GB
5. I am running Windows XP with Wins in a VM on my Fedora Linux Box
you wanted to go the Linux route that will also work in terms of the underlying comms.
Mike
Greg, I have everything running here under Server 2008 Enterprise 32-bit without any issues that I can tell of so far.
Hello Bob
What were you replying to virtualBOX or everything including 16 bit
doors running on Windows 2008 32 bit?
Hello Bob
What were you replying to virtualBOX or everything including 16 bit
doors running on Windows 2008 32 bit?
The latter in this case.
Your saying that 16 bit doors like Barren Realms Elite or Lord runs on
your Windows Server 2008 32 bit system?
Your saying that 16 bit doors like Barren Realms Elite or Lord run
your Windows Server 2008 32 bit system?
I've gotten Legend of the Red Dragon to run on that setup in the past,
yes. I am trying to get Legend of the Red Dragon up and running now,
but for some reason it doesn't look like the batch files are getting
called.
Also, do you have the door driver installed for WINserver by any chance? That might be an issue, too.
I have Windows 2008 Server 32 bit installed on one of my rack server
and none of the 16 bit doors work, I will download win2008 right from
Microsoft and do a fresh install and try it again though.
I'll get back with you.
Thanks
Greg
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 409 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 58:44:43 |
| Calls: | 8,572 |
| Calls today: | 2 |
| Files: | 13,225 |
| Messages: | 5,929,946 |