• Re: WINDOWS 2008 32 bit Server

    From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Thu, 14 Jun 2012 07:58:36 -0400
    From: GREG YOUNGBLOOD
    To: GREG YOUNGBLOOD
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1339675116.32.1338722627@winserver.com>
    References: <1338722627.32.1338181631@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 34

    On 6/3/2012 7:23 AM, GREG YOUNGBLOOD wrote to HECTOR SANTOS:

    On 5/28/2012 1:07 AM, HECTOR SANTOS wrote to GREG YOUNGBLOOD:

    Apparently Microsoft escalated the Security between the Level
    rings,
    between device drivers and the APPLICATION.

    Google the words:

    MSDN Windows 2008 VdmAllowed

    And you will find a series of articles. I am reading them now.
    Perhaps
    there is a registry VdmAllowed that I see one of the finds talk
    about.

    Microsoft made 1 promise back in the 1990s:

    Support WIN32 and we will guarantee it work with all Windows.

    Win32 is at the APPLICATION/USER level. They kept that promise but
    when it some to DEVICE DRIVERS, they never made that promise.


    Hello

    Did you find anything out on your end with Microsoft getting 16 doors to
    work with Win2008?

    Crossing fingers....

    Greg

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Fri, 15 Jun 2012 10:07:27 -0400
    From: GREG YOUNGBLOOD
    To: HECTOR SANTOS
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1339769247.32.1338181631@winserver.com>
    References: <1338181631.32.1338149359@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 51

    On 5/28/2012 1:07 AM, HECTOR SANTOS wrote to GREG YOUNGBLOOD:

    Apparently Microsoft escalated the Security between the Level rings, between device drivers and the APPLICATION.

    Google the words:

    MSDN Windows 2008 VdmAllowed

    And you will find a series of articles. I am reading them now. Perhaps there is a registry VdmAllowed that I see one of the finds talk about.

    Microsoft made 1 promise back in the 1990s:

    Support WIN32 and we will guarantee it work with all Windows.

    Win32 is at the APPLICATION/USER level. They kept that promise but
    when it some to DEVICE DRIVERS, they never made that promise.

    But Wildcat! didn't change, MS did. So it could help to post a message
    in their forums to see if they have work around.

    I am going to look for an HOPE that it is a security thing and they
    left a registry option to enable it.

    The problem with Microsoft is that someone finds a security issue for
    THEIR DEVICE DRIVERS, they do something that breaks others.

    The last time that happen was with RPC remote client/server
    communications where they broke the ability for Wildcat! Server to run
    on one machine and run clients, like wcOnline on another machine. To
    get it back, you had to change a registry option and WCSERVER.EXE had
    to say "its ok to run the old way." That was all because of THEIR
    SECURITY BUGS with PORT 450 and their DNS RPC server.

    If you want to help research or ask Microsoft directly, that will be
    great. But cross our fingers because if they BROKE it for 2008 and WCDOORNT.DLL no longer works, well, I don't know what do yet, but it
    ain't going to be a while if that is the case. It may not be a big
    deal, but its time to FIGURE OUT what they did and what is the
    solution. It was not our FAULT. :)

    Hello

    Did you find anything out on your end with Microsoft getting 16 doors to
    work with Win2008?

    Crossing fingers....

    Greg

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From BOBBY TODD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Fri, 29 Jun 2012 09:03:10 -0400
    From: BOBBY TODD
    To: GREG YOUNGBLOOD
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1340975232.32.1339769247@winserver.com>
    References: <1339769247.32.1338181631@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 7


    Did you find anything out on your end with Microsoft getting 16 doors to work with Win2008?

    If you are talking about 16-bit DOS applications running under the
    64-bit version of Server 2008, then they won't.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Wed, 04 Jul 2012 16:09:25 -0400
    From: GREG YOUNGBLOOD
    To: BOBBY TODD
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1341432565.32.1340975232@winserver.com>
    References: <1340975232.32.1339769247@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 17

    On 6/29/2012 9:03 AM, BOBBY TODD wrote to GREG YOUNGBLOOD:


    Did you find anything out on your end with Microsoft getting 16
    doors to
    work with Win2008?

    If you are talking about 16-bit DOS applications running under the
    64-bit version of Server 2008, then they won't.


    Nope I was talking about 32 bit Windows 2008, if and when the time ever
    comes and I move on to 64 bit I will use dosX to run my doors under a 64
    bit OS.

    Greg

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Thu, 25 Oct 2012 09:36:06 -0400
    From: GREG YOUNGBLOOD
    To: GREG YOUNGBLOOD
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1351172166.32.1339769247@winserver.com>
    References: <1339769247.32.1338181631@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 22

    Hello Hector

    I know your busy with Winserver 7.0

    But I know this would take you too much time to engineer a switch to use
    DOSX or the option to use DOS BOX being it is a stronger version of DOS.
    And also it is freeware on the internet for old DOS games and programs.

    I have posted on three Windows message boards about DOSX working with
    Windows 2003 32bit but not 2008 32 bit, have not heard a word yet.

    If you could point me too the right Microsoft message area for this topic
    it would help.

    Also I've been thinking about WinServer 7.0 but I have not seen any
    topics about what it is all about (improvements) Can you give a list of
    the changes so as I/We know what we are signing up for to upgrade to?

    Thanks

    Greg

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Thu, 25 Oct 2012 19:36:06 -0400
    From: MICHAEL PURDY
    To: GREG YOUNGBLOOD
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1351208166.32.1351172166@winserver.com>
    References: <1351172166.32.1339769247@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 54

    Greg

    You posted from yourself to yourself so Hector may or may not see your message.

    Wildcat! 7

    Hector has previously stated that Wildcat! v7.0 is essentially a recompile under the latest production version of Microsoft Visual Studio VC++. I
    believe once he is confident that base recompile is operating without issue then he will look to add new functionality.

    DOS

    There is no ROI for developers with regards to DOS or DOSx projects.

    The configuration most sysops has agreed on is:

    1. An up to date 32/64 bit OS
    2. Installation of a Virtualisation environment such as Virtualbox
    3. Install an old DOS friendly OS in the VM environment
    4. Install wcOnline in the VM and run DOS doors with the VM/OS

    Mike






    On 10/25/2012 9:36 AM, GREG YOUNGBLOOD wrote to GREG YOUNGBLOOD:

    Hello Hector

    I know your busy with Winserver 7.0

    But I know this would take you too much time to engineer a switch to use DOSX or the option to use DOS BOX being it is a stronger version of DOS.
    And also it is freeware on the internet for old DOS games and programs.

    I have posted on three Windows message boards about DOSX working with Windows 2003 32bit but not 2008 32 bit, have not heard a word yet.

    If you could point me too the right Microsoft message area for this topic it would help.

    Also I've been thinking about WinServer 7.0 but I have not seen any
    topics about what it is all about (improvements) Can you give a list of
    the changes so as I/We know what we are signing up for to upgrade to?

    Thanks

    Greg


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Sat, 27 Oct 2012 05:30:21 -0400
    From: GREG YOUNGBLOOD
    To: MICHAEL PURDY
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1351330221.32.1351208166@winserver.com>
    References: <1351208166.32.1351172166@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 24

    The configuration most sysops has agreed on is:

    1. An up to date 32/64 bit OS
    2. Installation of a Virtualisation environment such as Virtualbox
    3. Install an old DOS friendly OS in the VM environment
    4. Install wcOnline in the VM and run DOS doors with the VM/OS


    Hello Mike

    Could you give me a little more detail on this subject.

    Funnny I was going down that road already, I have VirtualBOX installed
    already and DOS in that environment my question is how do you go from
    when you make a command like (1) lord to run the door and a normal
    windows DOSx window opens to then opening a virtual window with DOS other
    then to a shared folder in that environment?

    Also do I only need wc online.exe in that DOS environment and what does
    that do for me?

    Thanks for the help.

    Greg
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Sat, 27 Oct 2012 07:08:40 -0400
    From: MICHAEL PURDY
    To: GREG YOUNGBLOOD
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1351336120.32.1351330221@winserver.com>
    References: <1351330221.32.1351208166@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 97

    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


    10/27/2012 5:30 AM, GREG YOUNGBLOOD wrote to MICHAEL PURDY:

    The configuration most sysops has agreed on is:

    1. An up to date 32/64 bit OS
    2. Installation of a Virtualisation environment such as Virtualbox
    3. Install an old DOS friendly OS in the VM environment
    4. Install wcOnline in the VM and run DOS doors with the VM/OS


    Hello Mike

    Could you give me a little more detail on this subject.

    Funnny I was going down that road already, I have VirtualBOX installed already and DOS in that environment my question is how do you go from
    when you make a command like (1) lord to run the door and a normal
    windows DOSx window opens to then opening a virtual window with DOS other then to a shared folder in that environment?

    Also do I only need wc online.exe in that DOS environment and what does that do for me?

    Thanks for the help.

    Greg

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    Date: Sat, 27 Oct 2012 14:39:19 -0400
    From: GREG YOUNGBLOOD
    To: MICHAEL PURDY
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1351363159.32.1351336120@winserver.com>
    References: <1351336120.32.1351330221@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 93

    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)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:06 2019
    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: <1351414164.32.1351363159@winserver.com>
    References: <1351363159.32.1351336120@winserver.com>
    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)
  • From BOBBY TODD@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Sat, 07 Dec 2013 18:27:22 -0400
    From: BOBBY TODD
    To: MICHAEL PURDY
    Subject: Re: WINDOWS 2008 32 bit Server
    Newsgroups: win.server.program
    Message-ID: <1386458842.32.1351414164@winserver.com>
    References: <1351414164.32.1351363159@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 33

    On 10/28/2012 3:49 AM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:

    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

    Or you could do like I did and go to savemyserver.com and buy a decent
    Dell server with the following configuration:

    Dell PowerEdge 860 Server
    2.13GHz Dual Core
    2GB RAM
    250GB SATA Hard Drive

    The cost with shipping and handling was $83.08 (which breaks down to
    $59.95 plus $23.13 for S&H). I have two of these boxes in my rack here at home -- one for web and email hosting and the other dedicated to the BBS
    and both running 32-bit Windows Server 2008 (non-R2) Enterprise. They
    don't come with rails or front bezels but I was able to find those for
    cheap on eBay without any issues. Here is a link to what I bought:

    http://www.savemyserver.com/dell-poweredge-860-server-2-13ghz-dual-core- 2gb-ram-250gb-sata-hard-drive/

    Their items may be refurbs, but they work well enough for a dedicated
    hobbyist BBS machine. Plus, if you want to add another SATA drive into
    the machine, there is a spot for another drive as well.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)