Subj : Re: WINDOWS 2008 32 bit Server
To : All
From : MICHAEL PURDY
Date : Thu Jan 31 2019 07:12 pm
Date: Sun, 28 Oct 2012 03:49:24 -0400
From: MICHAEL PURDY
To: GREG YOUNGBLOOD
Subject: Re: WINDOWS 2008 32 bit Server
Newsgroups: win.server.program
Message-ID: <
[email protected]>
References: <
[email protected]>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 121
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 processor overhead
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/27/2012 2:39 PM, GREG YOUNGBLOOD wrote to MICHAEL PURDY:
-> On 10/27/2012 7:08 AM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:
->
-> -> Greg
-> ->
-> -> Lets say you are a hobbyist sysop with
-> ->
-> -> 1. A single computer
-> -> 2. One Static IP
-> -> 3. A 64-bit non DOS Friendly Host OS
-> -> 4. Access to an older OS such as Windows 2000 or Windows XP
-> ->
-> -> Step 1
-> ->
-> -> On the 64 Bit Host computer you would install Virtualbox
-> ->
-> ->
https://www.virtualbox.org/
-> ->
-> -> Step 2
-> ->
-> -> Within Virtualbox you Would create a New VM for say Windows 2000/XP
-> ->
-> -> Step 3
-> ->
-> -> You would customize the VM as needed and in particular set networking
-> to a
-> -> Bridged Network Configuration with a static private IP
-> ->
-> -> Step 4
-> ->
-> -> You would follow the normal Wildcat! networking instructions for
-> setting up
-> -> a second machine running just wcOnline and the core DLL's
-> -> Refer to Hectors Knowledge base article on wildcat networking.
-> ->
-> -> Step 5
-> ->
-> -> Once your Host OS PC and VM PC Wildcat installs are talking to each
-> other
-> -> you would then setup the DOS Doors on the VM DOS Friendly machine.
-> ->
-> -> Step 6
-> ->
-> -> In DNS you would add a new A or CNAME record for the VM Machine say
-> ->
-> -> doors.mydomain.com
-> ->
-> -> Step 7
-> ->
-> -> On your modem/router you would redirect all Telnet traffic to the VM
-> Machine
-> ->
-> -> Step 8
-> ->
-> -> When everything tests OK you would switch the VM OS to Headless Mode
-> rather
-> -> than GUI Mode so that it becomes a simple task rather than a desktop
-> -> application
-> ->
-> -> Summary
-> ->
-> -> So you would end up with all your DOS doors running on the VM not the
-> 64bit
-> -> Host Machine. The only downside for a single IP Address would be
-> users not
-> -> being able to Telnet into the Host PC just the VM Machine. Naturally
-> if
-> -> you have multiple public IP'S then there is no downside.
-> ->
-> -> DOS
-> ->
-> -> I am aware of one sysop running DOS in a VM Under Virtualbox with a
-> very
-> -> old version of Wildcat! for local and dial-up access only. For IP
-> layer
-> -> access and to stay up to date with Wins a GUI TCP ready OS is a better
-> way
-> -> to go.
-> ->
-> -> I hope this helps
-> ->
-> -> Mike
->
->
-> Hello Mike
->
-> Thanks for the info, I'll be working on it tomorrow and see what I come
-> up with in the next week or two.
->
-> Thank you for your time and info, laughing I maybe ask something again or
-> do a lot of internet reading.
->
-> Greg
->
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)