#RUN DOSBOX FULL SCREEN DRIVERS#
#RUN DOSBOX FULL SCREEN UPDATE#
#RUN DOSBOX FULL SCREEN FULL#
#RUN DOSBOX FULL SCREEN SOFTWARE#
#RUN DOSBOX FULL SCREEN WINDOWS 8.1#

So, for about 9 hours, I tested alllll the updates for compatibility with the application (it was snapshot city).

#RUN DOSBOX FULL SCREEN UPDATE#

I figured it had to be related to an update somewhere down the line. However, on a whim, I span up a fresh Server 2003 VM and tried running the application via RDP on there. So TeamViewer worked as an intermediate solution for me (many thanks for that). Thanks for the comprehensive reply, I'll keep you posted. I have tried DOSbox, but encountered the same issue when accessed remotely. Hope either of these might help, otherwise best of luck trying to get it do-able until they can get it replaced.

#RUN DOSBOX FULL SCREEN FULL#

I tried Teamviewer (without installing the graphic driver) and am able to now control the system even with DOSBox up and full screen.

#RUN DOSBOX FULL SCREEN DRIVERS#

The ones I tried before had specific display drivers that would load an overlay.

#RUN DOSBOX FULL SCREEN SOFTWARE#

Previously, I tried a couple of different remote software for him, but always when the DOS window was fullscreen it would suspend the remote.

#RUN DOSBOX FULL SCREEN WINDOWS 8.1#

I set it up on a Windows 8.1 圆4 system for him.Īlso, have you tried different remote software? ini for fullscreen and windowed mode as well. ini to make it run a little faster and set some of the drives and settings, but it worked fine. I sadly have a customer who is still using a DOS based database system, which works fine in DOSBox. Would the 16-bit software run in DOSBox? It's only my second year in IT too (went straight from helpdesk to this), but I wanted a tough project to put on my CV. When I first got here 4 months ago they were running web servers off of Windows XP home machines (processing payments!), had no domain / ACL's set up, the 2003 server had never been patched as they didn't want to break any of the legacy 's been an uphill battle to say the least. They are out of business.īelieve me, if I wasn't a full time employee there's no chance I would support a situation like this.

They didn't want to upgrade, I didn't think they were 'good money' so we parted ways. Their remote offices had to use Metaframe or they couldn't print/couldn't run fullscreen. Over a dozen years ago I had a client that refused to see the writing on the wall and continued using a medical billing/inventory system that used DOS clients running against a Pervasive database. I know it’s a long shot to say the least.Īre there any alternative solutions here that I’ve missed?īack in the day you had to add Citrix Metaframe to NT4/Win2K Terminal Server get fullscreen DOS support / printing support. Could we lock a particular user down via GPO to only be able to log on to the host and then connect to a VM (without the ability to modify anything)? Almost like kiosk mode on the host. Obviously, we really want to avoid this as it could end in disaster.

When we move onto the 2012 server we’ll have rewritten the code so that it runs via scheduled task and no-one apart from me has to touch the server.Ģ) The last person on-site logs on to the Hyper-V host, goes into the VM that way and runs the code. As far as we can see, we only have two options:ġ) Ideally, try to suppress the NTVDM error so that the last person on-site can remote into the server and run the task. We’ve tried applying MS hotfixes to the problem but to no avail.

The ntvdm error also still shows up in Event Viewer when you run the script directly from the machine, but it doesn’t cause any issues. However, this happens about 200 times during execution, so its not feasible for someone to sit through it closing all the error boxes. This doesn’t actually cause the script to crash, but rather just wait for input. Part of the code requires it to go into fullscreen mode, which RDP doesn’t like. The big issue now though is we can’t run the overnight script via RDP. I am currently in the process of virtualising the 2003 server in Hyper-V – not an ideal situation obviously, I’d rather move straight to a 2012 VM, but our programmer needs time to re-write all the code to run on an 圆4 system and I want to move off of the 10 year old hardware in the meantime. They couldn’t run it via scheduled tasks as it needed to be run in interactive mode which would require someone logging on anyway, and our closing time is not written in stone and can change. Before I joined the organisation, this was being kicked off manually on the 2003 server every night by the last person to leave the premises (I was horrified too, don't worry). We have an overnight run which is a piece of legacy 16-bit code. I’ve got a tricky problem and I’m out of ideas:

Run dosbox full screen