Windows 98 Vesa Driver For Mac

I have been wanting to play the old Lucas Arts adventure games (Sam & Max, Day of the Tentacle, Indiana Jones, etc.), but I can never seem to get them working with modern hardware and software (sound blaster live and win98). I am putting together an old box with the purpose of playing only these games, and I am wondering if anyone knows the best combination of hardware and software to get these games to run well.

Do I need Sound Blaster 16 and DOS, SB16 and Win98, or, most importantly if I need DOS, can I dual boot with DOS and Win98 so that I can stay networked? I would say the best bet is to use a SB16 card.

Although, it could work if you have SB LIVE with the SB16 emulator for DOS. I have tried the emulator, and it works fine (for Duke3D). If your running it in pure DOS, your going to need a few files, like MOUSE.COM. Your gonna have to troubleshoot. Use the MEM command in DOS to check your free base memory. I'm not sure how much that Lucas Art game uses, but remember, in old DOS games you usually only have 640K of DOS memory to work with. If it requires 200K of BASE, you better make sure you got it.

I had a few problems with memory with newer PC's, but it can all be worked out. And about the Dual-booting, I have never tried that. I have one harddrive with DOS, and the other with Linux/Win98SE. I don't know if it would work though.

Because Win98 uses DOS 7.1 to run. And if you were to install, lets say, DOS 6.22 - then you have just installed a different version of DOS on your machine, and maybe this would affect Win98.

Besides, DOS 6.22 is only FAT16 with means you can't have a harddrive bigger than 2 gigs without splitting it into different partitions. Hope this helps. 'And the difference with Windows is.'

Windows 98 Vesa Driver For Mac Pro

The difference between MS-DOS 6.22 and MS-DOS 7.1 (Win98)?? I believe DOS 6.22 was released in like 1993 or 1994. When I was in elementary school!

Windows 98 Vesa Driver For Mac Os

DOS 7.1 I believe was released in 1997. That's a whole 4 years, for one.

For two, the COMMAND.COM is totally recompiled and modified. For three, DOS 7.1 was the turning point in DOS, everything after it sucked!! Four, the.Memory management. of DOS 7.1 is totally different than that of DOS 6.22 (which is one of his problems). I could sit here all day and do this hehe.

Quote: The difference between MS-DOS 6.22 and MS-DOS 7.1 (Win98)?? I believe DOS 6.22 was released in like 1993 or 1994. When I was in elementary school! DOS 7.1 I believe was released in 1997. That's a whole 4 years, for one. For two, the COMMAND.COM is totally recompiled and modified.

For three, DOS 7.1 was the turning point in DOS, everything after it sucked!! Four, the.Memory management.

of DOS 7.1 is totally different than that of DOS 6.22 (which is one of his problems). I could sit here all day and do this hehe. I mean it as in you said that what works on DOS 6.22 might not work on DOS 6.20 as in what works in Win95 might not work in Win98, or Win95 the next day in fact!! Sammut's right about the differences. One very key difference is how with Win95 (DOS 7.x depending upon your version of Win9x, also reported as DOS 6.95) that the command.com file breaks MS's rule about.com files being no larger than 64k in size.

BTW, I've had very good luck running all sorts of old DOS games in a DOS 7.1 clean boot (with config.sys and autoexec.bat statements). Then again, I'm an old DOS wonk who actually made a boot menu and didn't use the Win9x boot menu.

DOS 7 and later is useful in how much stuff you can load in the HMA, and expanded memory areas that would normally take up conventional memory space. The Creative Labs.SYS loader is very useful to load.SYS (usually driver files, like mouse.sys, etc) files at the command line or within the autoexec.bat file. It's called CTLOAD.COM or CTLOAD.EXE and can be found on their ftp space. You can optionally just make an autoexec.bat and config.sys and put it on a boot floppy with appropriate sound/Vesa drivers, just for games booting, or you can even make the 'RESTART IN MSDOS' menu option mean something for you, by adjusting the DOSSTART.BAT batch file which will act as an autoexec.bat file when restarting in MSDOS mode (sort of like putting windows in hibernation or task switching out of it, but not really). You'll need the CTLOAD program from Creative Labs then, especially for the MSCDEX.EXE file or for the IDE CDROM Driver file. I've played everything from The Ancient Art Of War (At Sea as well) to Omega to various copies of Battletech to Doom 1/2 to WolfenStein 3D. I've even run all the Ultimas, save 7-8 (they have their own memory manager) as well as Ultima Underworld 1 & 2 and all the DOS Wing Commanders.

Depending upon your video card and the video bios, you may or may not need a VESA driver for it, or you may have to fake it with a generic driver to get it to run old 2D games that rely on VESA. SciTech's Display Doctor is a good start, but that's a time limited shareware.

Check your manufacturer's website and see if there's anything there in terms of VESA driver support. In theory, every modern video card is capable of it as a legacy support item, but as it's a legacy support item, it's probable that most everyone's phased it out over the last 3 or 4 generations of video cards. There's also free VESA drivers available in some situations (Matrox is notable for having some third party software available for free). And don't forget, that as fast as your video card is, in Windows, it may seem rather pitiful in DOS, when it's just used as a dumb framebuffer card. Your CPU will matter a bit more, as anything under 300mhz may stutter on more complex scenes. Heck, the video card's DOS 2D performance may become the bottleneck.

If you don't have the exact CDROM driver for your CDROM drive, you can get away with any of the ones on a Win98/98SE boot disk. The OTI driver is preferrable, as their firmware/interface chip is used in the majority of IDE CDROM drives, IIRC.

Copy statements out of the Win98/SE boot disk autoexec.bat and config.sys files as necessary. If you need help with the autoexe.bat and config.sys, post here and I'm sure you'll get help.Agent Monkey.

I apologize for not being clear. Windows 7 Pro is the host system, FreeBSD is the guest OS in VirtualBox running in Windows. My concern with running X.Org virtually is: what video driver do I select because pciconf -lv doesn't show a virtual graphics adapter listed in make config. I'm running FreeBSD on top of Windows 7 Pro because I have a new Optimus-based laptop that FreeBSD doesn't want to run on, and most of my work is done on previous FreeBSD systems. So I need to set up the environment on the Optimus-based system before I move all my data from the old system. The new system is an i7 Haswell system with 12 GB of memory, and I'm trying to tweak as much as I can so FreeBSD feels like the resident system - and so far, so good. I'm just not confident about X.Org and want to have all my ducks-in-a-row before I start delving deeper.

Section 'Device' ### Available Driver options are:- ### Values:: integer,: float,: 'True'/'False', ###: 'String',: ' Hz/kHz/MHz' ### arg: arg optional Identifier 'Card0' DRIVER 'VESA' VendorName 'InnoTek Systemberatung GmbH' BoardName 'VirtualBox Graphics Adapter' BusID 'PCI:0:2:0' EndSectionNote the DRIVER 'VESA' part. Provided that X.Org loads the vboxvideo driver simply replace the VESA with vboxvideo (Capitals only used to highlight). The file should now read.