I actually recall I used to play it on a Windows 98 system so I know it runs on higher. The game is Mechwarrior 2: Mercenaries which was designed to run on Windows 95 or MSDos. I'm using a Macbook Pro OS X 10.5 that I bought secondhand from a friend and what I'd really like to do is play an old disc I used to play on my PC years ago on the Mac. I'm aware similar questions have been asked before, but I'm having a pretty specific issue. Once Windows is working and has its own CD ROM driver (seperate from the DOS one that appears to be in this CD1.SYS file), the cure is simply to "REM out" the offending line in CONFIG.Hey everyone, this is actually my first post. So be aware that the word "Banana" might not be the only pain-in-the-ass side effect of this mysterious bug!īasically, if there is still a line "DEVICE=cd1.SYS /D:banana" enabled in the DOS's CONFIG.SYS file then you will be unable to process ANY file that has the name BANANA under the subsequent installation of Windows (including Banana.ppm, Banana.ANI etc) AND THIS will prevent things like the installation of Win95Plus! and indeed any other stuff that has files with the name Banana in them. However, it may merely be due to some setting that is used when installing either the CD or SB driver into the underlying DOS operating system via WIndows, and letting the installer choose its own device names. There's a mysterious side-effect about the word "Banana", which by it's nature makes me curious as to whether it might be an Easter Egg. I have no idea which combinations of VMWare, DOS, and either MSCDEX or the SoundBlaster driver installer (I'm really not sure which), got me into this strange situation with Windows 95 and Microsoft Plus, but.įor some bizarre reason I once had a situation whereby the CONFIG.SYS file had the following entry (not created by me): DEVICE=cd1.SYS /D:banana
0 kommentar(er)
