16-bit MS DOS subsystem This system does not support fullscreen mode
Det funkar dock att öppna på XP-datorer så det är nån inställning i Vista. Är det någon som vet hur jag kan göra för att få bort detta problem. Nån som har Vista kan ju ladda ner Jones in The fast lane själva också och testa om det funkar för er Tacksam för hjälp Jocke [inlägget ändrat 2007-10-21 23:19:47 av jocke88] Länk till kommentarDela på andra webbplatserMore sharing options... .MPostad 22 oktober, 2007 .M
Postad 22 oktober, 2007 Om det är ett gammalt dos-spel. Prova köra det med DOSBox istället.
http://dosbox.sourceforge.net/
Länk till kommentarDela på andra webbplatserMore sharing options... We have an overnight run which is a piece of legacy 16-bit code. 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). 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. 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 x64 system and I want to move off of the 10 year old hardware in the meantime. The big issue now though is we can’t run the overnight script via RDP. Part of the code requires it to go into fullscreen mode, which RDP doesn’t like. It throws up a ntvdm.exe hard error. This doesn’t actually cause the script to crash, but rather just wait for input. However, this happens about 200 times during execution, so its not feasible for someone to sit through it closing all the error boxes. 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. We’ve tried applying MS hotfixes to the problem but to no avail. As far as we can see, we only have two options: 1) Ideally, try to suppress the NTVDM error so that the last person on-site can remote into the server and run the task. 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. 2) The last person on-site logs on to the Hyper-V host, goes into the VM that way and runs the code. Obviously, we really want to avoid this as it could end in disaster. 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. I know it’s a long shot to say the least. All i need is to run it fullscreen. Strangely enuf, on another PC, with the same Windows 7 loaded, the program is working perfectly, with fullscreen. Surely there is something that has to be adjusted on my PC. The lack of support for full screen DOS Command Prompt in Windows Vista, Windows 7, Windows 8 and Windows 8.1 is a big annoyance especially for those who still playing games for DOS and Windows 3.1/9x era, use legacy software such as WPDOS or programmers who frequently switch to command prompt to use DOS based programming language such as PASCAL. It happens because in these OSes, the Windows Display Driver Model (WDDM) based device driver for the graphics card does not support the running of DOS video modes. There is no simple solution to this no support for full screen window in Windows Vista, Windows 7, Windows 8 and Windows 8.1. In almost all possible workarounds, you are almost guaranteed that your Windows Vista, Windows 7, Windows 8 and Windows 8.1 will be broken in some way, at least on the part on Windows Aero. You will lose the nice Aero Glass interface if you attempt any of these trick, plus other unknown side effects. Workaround to Run or Open Full Screen Window Mode Workaround 1: Use XDDM driver instead of WDDM driver for video graphics adapter In another word, install the Windows XP video card driver for use in Windows Vista, Windows 7, Windows 8 and Windows 8.1. If the video graphics card hardware supports Windows XP driver, you can download the Windows XP driver for your video hardware and install it under the Windows. However, be warned that using XP driver on display adapter may crash your Windows system randomly, so save your works before proceeding and use with care. Note: This solution has been recommended by Microsoft in KB926657. To install a Windows XP video driver under Vista, just follow the procedure listed in the guide below. The steps should work for both NVIDIA and AMD ATI video graphics accelerator card.
Workaround 2: Use Standard VGA Graphics Adapter video graphics driver Similar with method 1, but use Windows Vista, Windows 7, Windows 8 or Windows 8.1’s built-in Standard VGA Graphics Adapter driver, which offers greater stability and compatibility, but a lot less functionality and features support. The following steps guide you on how to install the Standard VGA Graphics Adapter.
Once computer rebooted, you should be able to open programs or command prompt shell in full screen window. You may need to set the resolution again, as everything related to display settings is likely to be reset. If you want to reverse this procedure and install back the video display card’s manufacturer driver, follow the same instructions again, but choose the option to let Windows automatically install the appropriate software for your system instead of browsing your computer for driver software. If you unable to do so by clicking on Properties button on Adapter tab, go to Device Manager and directly select Update Driver Software on right click context menu. Workaround 3 – Using DOSBox DOSBox is a Intel x86 and DOS emulator for Windows. The open source DOSBox application runs up a shell window which emulates a DOS environment complete with sound, graphics, mouse, modem, etc., and allows legacy DOS apps and games to be ran and play on it. DOSBox handles all requests between Windows and the DOS window, memory allocation, control CPU speed, and allow tweaking of sound card emulation, graphics type, key mapping, mouse sensitivity, resolution, full screen mode and etc. Although DOSBox cannot add Windows features to DOS programs that are run on DOS systems, and some features of DOS in native mode are not present, but its usefulness is still great in allowing almost all currently-available 32-bit versions of Microsoft Windows – Windows 95, 95b, 98, 98SE, ME, NT4, XP, 2000, 2003, Vista and 2008 to run legacy apps and games. Some tweaks and configuration have to be done in order to get DOSBox running to play your games or launch your old application software. Basic Setup and Installation of DosBox wiki provides a guide on how to use the DOSBox. As DOSBox emulates DOS, you will have to deal with lots of command line syntaxes in command shell. If you’re not familiar with command prompt, there are a few GUI frontend interface for DOSBox, which presents all settings in typical Windows interface, and allows users to attach different profiles with different configuration optimal for different DOS games or programs. Such front ends include D-Fend (no longer available), D.O.G. (no longer available) and DBGL: DOSBox Game Launcher Note that while using DOSBox, it’s best to disable User Account Control to get the best performance and so that DOSBox can properly emulates sound, VGA color and CPU speed. During the DOS era there is simply not such thing as functionality restriction based on user account and user level, thus any limitation may cause problem to emulated apps. Another issue is Windows Sticky Keys, an accessibility features for physically-handicapped users. Sticky Keys are activated by pressing a particular sequence or combination of keys which a normal user seldom and unlikely stumble across, such as pressing Shift key 5 times continuously. But these sequence of key pressing may be needed during DOS gameplay. Worse is that DOSBox doesn’t handle this properly and it doesn’t partition keyboard or mouse activity away from the host OS. So you properly need to disable Sticky Keys permanently so that it won’t suddenly appear and disrupt game play. Again, using DosBOX and/or its front-end GUI may also caused some apps or games to suffer from abnormal behavior such as system randomly crashes or refuses to run altogether. |