General retrocomputing hardware and software discussion. Get help, give help, show off, shoot the shit, discuss your hobby.
Welcome: Windows 1.x-3.x/9x/NT, MS/PC-DOS, OS/2, Classic Mac OS 1-9, Amiga, 8-bit home systems, CP/M, Legacy Unix platforms, anything pre-1999 you can possibly think of
Tolerated: Windows 2000, Windows Me, OS X on PowerPC systems, GNU/Linux (relating to retro hardware)
Tolerated, but discouraged: Retro consoles (there's /vr/ for that guys), DOS game emulation (/vr/)
pls go: XP, OS X on Intel systems
>daily reminder that /retro/ is a no bullying zone
>daily reminder that you can filter tripfags you don't like for whatever reason so we don't have to hear your whining
These threads need more Windows NT. I think to make these threads more interesting, we should make challenges for other anons to try to complete with their old technology
>inb4 install gentoo
>being the reason the greentext is there
Just run System 7 on it, you'll have a larger base of applications to choose from that will run much better on that system.
Why use something that old to do the exact same thing you could be doing far better on a modern platform?
I appreciate the help, but I don't think that will work. It says there is no floppy drive support, but the computer has no cd drive: just a floppy drive. Also, the writer says that he just gets by with 5MB RAM, and I have 20% less than that.
You'll have to get an AppleCD drive and an HDI-30 SCSI cable to connect it, along with a RAM upgrade. Unfortunately you're stuck running Mac OS unless you want to do either of those things.
How about this? I tried to make it as even as possible. Extra points for doing these things on real hardware and not in a VM/emulator.
>I've already done half of these
>It wasn't considered retro back then
I have a 1994 SPARCstation 5 with Soalris 9 installed. Only bad thing is my NVRam went bad 2 weeks ago, and I can't do anything until I Fix/ replace it. Does anyone know where to get an NVRam chip for a SS5?
I tried to make some things easier and some harder. I also wanted some of them to be common tasks that people actually did back in the day, and others to be strange tasks that people don't do very often, like playing games on NT 3.51 and installing Windows Chicago on a real computer. Also my old videos of playing Unreal and Deus Ex on NT 3.51 don't count.
I've been thinking about trying to get my hands on an old computer, something like pic related, with intact period-correct stickers, gutting it, and using the case for a new build, preferably something beefy to further contrast the case's claims
My only concern would be whether one of those cases has sufficient cooling/space for modern components
Nevermind, got it working.
Any browsers or other software you guys want to see? Got full archives of WinWorldPC and Simtelnet.
>My only concern would be whether one of those cases has sufficient cooling/space for modern components
Those generally took gimped MicroATX mobos. Also, half-size PSUs. So probably not. Some really early ones even used Baby-AT mobos.
As for cooling, don't count on it.
Maybe a low-power ITX or mATX board might do okay in there, like one with a passively-cooled CPU?
Pavilions were shit new and they're even shittier now, both hardware-wise and case-wise go for the cases Dell was using just before the switch to the black monstrosities we all love to hate now or certain HP Business systems that were mostly ATX-compliant except for the LED connectors that were all put in one block.
An old ATX whitebox case is fine too.
Heh, I actually have that thread in another tab at the moment.
Pretty cool shit. I wouldn't mind having a Color NeXT system. Though I can pretend by installing MidnightBSD or Debian with Window Maker/GNUstep.
IE sees the amount of JS before the page load and says "fuck that, general protection fault"
Well, what do you know.
Looks like Opera survived.
Remember when the internet was full of interesting, original content?
Maybe if I had a 4chan Pass, i could do this.
You tell me.
>CGA, Tandy, VGA Mode 13
>set video mode
>write pixel data to VRAM
>switch 20 confusing registers around depending on whether you're reading or writing pixel data
"This field is used in Write Mode 0 and Write Mode 3 (See the Write Mode field.) In these modes, the host data is rotated to the right by the value specified by the value of this field. A rotation operation consists of moving bits 7-1 right one position to bits 6-0, simultaneously wrapping bit 0 around to bit 7, and is repeated the number of times specified by this field."
I mean, what the fuck is this?
From a programming standpoint, EGA and VGA modes (excluding Mode 13) all work essentially the same. You have four planes for the red, green, blue, and intensity data, which are either 8, 16, 32, or 64k in size depending on the mode used. Only one can be seen by the CPU at a time, although all four may be written to at once depending on the register settings.
And yes, the programming of them requires a lot of register writes and is slow and complicated, which is why Mode 13 (so easy a caveman can do it) is recommended despite its low resolution.
To clarify, if you're in Mode D (320x200x16), the planes are 8k in size and go from A000:0000 to A000:1FFF. If you're in Mode 12 (640x480x16), the planes are 64k and occupy the entire A000 segment.
I have no idea either why you have to bank switch the planes in the lower modes since there's no reason you can't fit all of them into the VRAM segment.
I purchase a new car radio for my car and i got one with a cd player so i can have that retro feel of using CDs again, USB is more comfortable but nothings beats that orgasmic feel when the mechanic hungrily swallows your CD in
>surf the web on Windows 3.1
Easy! Trumpet Winsock TCP stack and Opera, IE5 & Netscape 4.
>Play Doom on a network via serial port
Do null-modem cable duels count?
>Warp us away to the land of OS/2
OS/2 Warp 4 is one of my favorite OS. I don't have it installed for the moment, but a few month ago, yes, i had it on an old Pentium II.
>connect to a BBS
Yep, and a Dial-up one! Nostromo BBS+44 1582-600882
>Hook a vintage CRT up to a modern computer
My Samsung Syncmaster is from 1999, it can go up to 1920*1440, and has a max refresh rate of 180Hz, I don't know why I should buy an LCD when this monitor is better than most of them.
>Play game on your Amiga
Dungeon Master, Captive, Star Control and Hybris.
>Post an old PC with an x86 CPU not made by AMD or Intel
My Victor V86p has a 80c86 made by Oki, and I don't know if it counts as it's not really a PC compatible, but my PC-9801N has a NEC CPU.
>Surf the Web on Netscape Navigator
On my Windows 2000 machine, and on my Windows 3.1 too at first (I use opera and internet explorer more)
>Post an old PC with an x86 CPU not made by AMD or Intel
Not mine, but the exact same model.
>live in postsoviet country
>some dude sellin' SGi Indy on local board for ~$70
>mfw there's no display/controllers included
98SE isn't really retro but it is a nostalgia trip.
Here. This draws a couple of colored boxes in Mode 12:;VGABOXES
st_seg segment stack
db 512d dup (?)
planesegs dw ?
oldcurs dw ?
oldscr dw ?
textscr dw 0b800h
main proc far
jmp short cleanup
;draw a few boxes
;restore old text
;restore old cursor
drawpixel12 proc near
Part 4:mov cl,bl
moveplanes proc near
Finally, Part 5:;---------------------------------------------------------------
fill_box proc near
Nice. I picked up x86 assembler again recently, playing around with N(dis)ASM and Ralf Brown's Interrupt List.
I took the ATXOFF.COM tool apart, which can be used to turn off almost any ATX system from DOS using APM:.section text
xor bx, bx ; System BIOS = 0000h
mov ax, 0x5301 ; APM CONNECT REAL-MODE INTERFACE
int 0x15 ; Miscellaneous system services interrupt
xor bx, bx
mov cx,0x102 ; APM version 1.2
mov ax,0x530e ; APM DRIVER VERSION
int 0x15 ; (inform APM that we understand more than version 1.0)
mov ax, 0x5307 ; APM 1.2 TURN OFF SYSTEM
mov cx, 0x3 ; constant
mov bx, 0x1 ; constant
ret ; return to DOS on error
Some of this was from a code listing I found online, but made modifications to. The original listing was set up as a COM file and I rearranged it to be an EXE.
The original listing used INT 21h Function 4Ah to set the total allocated memory to 64k, but I took that out because it's not needed for EXE files (COM files normally commandeer all available memory)
The BP register is normally used as an index into the stack segment. You load it with the offset of the data you're trying to access there. That code means "Load AL with the contents of the memory location pointed to by BP plus 4 bytes" (meaning that it uses the address 4 bytes above the one in BP). Unless you use a segment override (eg. mov al,es:[bp+4]), the BP register by default uses whatever segment the SS register is set to.
SP, BX, SI, and DI can also be used as pointers, but they normally point to the data segment (DS) unless an override is used (excluding SP, which of course points to the stack segment). When using 32-bit code however, any general purpose register can be a pointer and you're not limited to BX, SI, DI, SP, and BP.
Making a booter program on Amiga allow you to use assembly the way you cant. Otherwise, for Workbench applibation programming, you're better off with C and some assembly routines if you really need speed.
Well yeah, because you don't have to worry about code being relocatable so you can use absolute JMPs instead of relative ones.
>Otherwise, for Workbench application programming, you're better off with C and some assembly routines if you really need speed
This was the norm in the Amiga era; games would be programmed in assembly while applications used C.
>This was the norm in the Amiga era; games would be programmed in assembly while applications used C.
I also think that it's easier to use the ROM routines in C than in assembly.
That reminds me of my Cyrix 6x86. I think it ran at 166 MHz. Always used that instead of my Pentium MMX. Think I'll reuse it if I were to build a computer for MS-DOS games and the early win9x games. My coppermine is usually too fast for those.
Just an example, don't assume this is about me:
>Be 14 in 1998
>Win 98 was on my computer
>1998 was 16 years ago
>Now 30 years old
>Nostalgia for what could plausibly have been my first computer, in an age period many adults are nostalgic for.
Is it really that implausible?
Sounds legit. I'm 28 years and 9 months old. A lot of the stuff from that era makes me feel good. Especially the music.
I skipped Windows 98 tho. Used Windows 95 until I replaced it with Windows 2000 in 2002-2003.
An the Amiga? Load the right library, set the parameters in the registers, call the routine, close the library.
It's not easy to code stuff like this on an Amiga. It's way easier to code stuff like making a color-cycling raster.
Besides, Amiga doesn't have a real text mode anyway, just 320 and 640x200 graphics.
There's also the interlaced mode 320 & 640*400. And that's if you use your machine in 60Hz mode, in 50Hz mode, the vertical resolutions are 256 when progressive and 512 when interlaced.
For comparison, writing directly to the VRAM (these examples put an A in the upper left corner of the screen while the previous ones put it wherever the cursor happens to be):
>Commodore 64lda #65
And since you can't just poke random video RAM locations with Workbench running, you probably have to set up a window box and put the graphics data in there. Amiga is quite a lot more complicated than C64 or PeeCees.
It's a newer architecture of course, introduced in 1985 while the C64 and PC predate it by 3 and 4 years respectively. By the mid-80s, the Mac had come out and it was obvious that GUIs were the future direction of everything. PCs only stuck with text mode DOS for as long as they did due to the need for backwards compatibility.
FWIW, the 68000 was a newer and more advanced CPU than the 8086 and more suited for running a GUI.
The 8086 was the last 70s CPU (belonging to the age of the Altair 8800 and CP/M) and the 68000 was the first 80s CPU (belonging to the age of GUIs and mice).
The problem is that you can't ask its location. You have to tell the Copper coprocessor to write sutff on VRAM for you:
It's better like that because the blitter contained in the copper is faster at moving data in memory (it can alway access it while the CPU can only 1 cycle out of 2), and have a higher priority at accessing it (it can deny the CPU the right to access RAM if it has a lot of shifting to do).
Yeh, PCs have always had the misfortune of being overburdened with backwards compatibility. For example, there's no reason for 40-column text modes to exist on VGA except for CGA compatibility.
I was just redirected to this thread so here we go.
Nope, that's an excuse. Doom run fine on Amigas that aren't Amiga 1000, 500, 600 and unexpended 2000. Remember that these machines use a 7MHz 68000, which is the 680x0 equivalent of the 8086. Go run Doom on a 8086 PC and tell me how fast it runs. Doom needs at least a 386 or even a 486 to run correctly, which in term of 680x0 CPU translate into 68030 and 68040.
Doom running on an AGA-based Amiga with a 68040@33MHz run as fine as on a 486@33MHz based PC: yes, the Amiga render textures 3D scene 3 time slower than a PC, but the 68040 is 3 time faster than the 486 CPU when it comes to Floating point operations, needed when it comes to 3D stuff.
No, the reason why John Carmack said Doom wont run on Amiga is because:
- Brits were all using unexpended Amiga 500
- The game wouldn't be allowed in Germany
- The game will be pirated in Eastern Europe
- Northern Europe and France were switching to PC clones.
>Remember that these machines use a 7MHz 68000, which is the 680x0 equivalent of the 8086
It's not really an exact comparison because the 68000 has internal 32-bit registers and a 24-bit address bus, neither of which applies to the 8086. The 286 is closer, but still only 16-bit registers.
I'm speaking in term of elderliness in the CPU family. Of course, all 680x0 CPU are superior to their x86 equivalent, the 68060 excepted (if only Motorola really worked on it instead of just screwing it and jumping on the PowerPC train).
INT 21h Functions 48h, 4Ah, and 4Bh are used for dynamic memory allocation. They reserve a memory segment for the application, the size of which is determined by the number of paragraphs specified in BX (paragraph=16 bytes, the minimum allowed segment size). If allocation is successful, the segment address is returned in AX. When exiting a program with INT 21h Function 4Ch, all allocated memory blocks are freed.
As I mentioned, EXE files by default only allocate as much RAM as the program itself occupies, but COM files for some reason reserve all available conventional RAM unless you use Function 4Ah to reduce it to some smaller value.
They didn't remotely reach that back then either, not with their fast-rotating server storage magnets.
Trying to push data through a parallel bus like IDE or SCSI wasn't effective in the long run anyway due to effects like crosstalk and transit time variations.
That's why all parallel busses on the PC (including PCI) have been dead for almost a decade now.
>As I mentioned, EXE files by default only allocate as much RAM as the program itself occupies, but COM files for some reason reserve all available conventional RAM unless you use Function 4Ah to reduce it to some smaller value
For anyone not familiar with DOS programming, COM files are executables which have no separate data or stack segment; the segment registers are all set to the same value and everything (code, stack, and data) must fit within one 64k segment. For small programs, COM files are convenient since they have a flat memory layout. COM files always begin program execution at offset 100h and have no header information. The stack begins at the top of the segment (offset FFFE) and moves down from there.
EXE files have no size limit (beyond the available RAM space on the PC) and may have multiple code, data, and stack segments. They also contain a header which DOS uses to set up the segments prior to passing control to the program. The stack segment begins at whatever value you set up (so if you set a 512-byte stack, it begins at offset 200h). A separate stack segment is not required, and if you don't set one up, the data segment will be used for the stack (in which case it starts at FFFE)
Still find too many motherboards with that. I was looking for one without PCI when buying my new motherboard, but ended up with one with PCI slots anyways since the ones without had fewer SATA ports.
Having too few SATA ports is suffering.
When did ISA slots stop appearing on mainstream motherboards? My Socket 370 board has nothing but PCI and one AGP Pro slot. My Slot 1 board has 3 ISA slots.
man, i spent too long just using an lcd
got the contrast/brightness balanced out on my 'new' tv hooked up to my computer, and have just setup an 853x480i mode (16:9)
the tv also has a 16:9 geometry mode, meaning i can use the full 480 lines while displaying 16:9 media
even playing hd media on it looks far better than on my average 1080p computer monitor, mainly due to the contrast, it's the middle of the night atm, and i've got hellsing playing... dark scenes leave the room pitch black, but still everything in the scene is clear and visible, and flashes of light colors are blindingly bright at the same time
the hit in resolution is no competition next to the contrast advantage, i don't know how i missed this when moving from a crt pc monitor to lcd
there's really no way to show the way it looks by photo, but it's really a huge difference compared to my lcd
Many CRTs aren't really black either. Seen a few too many bright grey ones. At least they don't blind your eyes when they do try to display a black picture.
My LCD isn't very comfortable at night.
t-that was me
Those are still bretty good, though, I've just got a 100 MHz R4000, a 540MB disk and IRIX 5.3, which can't run shit.
Thrift store back room, can pick whatever I want out of a dumpster for $5 each regardless of what it is.
Also Craigslist, industrial surplus, work and misc. contacts through friends and family.
Should I email this guy? Apparently it still spins
Well nothing, really. But just look at all those platters!
I sent him my # and offered $100
If anyone was around for the discussion about HP Vectra systems we were having a couple threads back, I found my gutted 386DX-20 box in a pile of shit while cleaning up the shed and checked out the back, they used standard AT keyboards but HP-HIL mice.
The usual candidates are debian, slackware, arch, and light weight derivatives.
A source based distros like gentoo and crux can work well (there are others too), but you must be ok with spending hours compiling big packages like Firefox. It took about 2 hours to compile Firefox on my E6300 a year ago and you will need more than 2GB of RAM to do so. Should be easy and cheap to get a 4GB DDR2 set from ebay. I think I paid 20 dollars for my kit. I think you'd be better off with a distro that has precompiled backages if your laptop doesn't support that much RAM.
I misread your post, I dunno, he probably didn't see it or know we were doing these things now, what do we have to do with that?
I think it's better as its own thread anyway since it would probably otherwise be drowned out by other discussions.
It is easy to forget how poorly 3D games ran on contemporary hardware back then.
Anything higher than 640x480 seems unplayable to me now, but I can remember being happy with the way Halflife ran on my Pentium II + Riva TNT. I played with the resolution set to 1024x768.
Last year when I played Mirror's Edge I had to lower the texture quality to stop the framerates from dipping down to 40-50 FPS. I thought the sudden drop in framerate was unbearable.
You can probably play it in an emulator.
> Get ahold of a Toshiba Satellite Pro T2155CDS
> 486 DX4 75MHz, 20MB of RAM,
> Drive is wiped
> Currently running Windows 3.1
Where do you guys find drivers for hardware this old?
Toshiba has some on their website, but I can't seem to find audio drivers anywhere, and it's got some sort of goofy ass chipset.
I already threw a 16MB stick in, so it's at 20MB total.
Don't judge me, I need drivers for muh DOS games. I figure I'd rather run them natively tan use DOSBox.
I could use 95, but that's just more hard drive space being eaten for nothing more than a fancier GUI. I figure the 75MH 486 is probably too slow for DirectX games.
Thank you, I'll give this a shot.
That's true, but I'll still need realmode DOS for games that either don't play well when run under Windows 95, or ones that do, but are close enough to the performance threshhold that the extra layer takes them from playable to unplayable.
I'm considering installing 95 anyway, since I have a PCMCIA ethernet card and it might be fun to dick around with IE5 and see how fast a machine with 20MB of RAM chokes on the modern internet.
>That's true, but I'll still need realmode DOS for games that either don't play well when run under Windows 95
Just go into real mode by hitting F8 on the POST beep and selecting Command Prompt Only from the startup menu.
I have a Thinkpad with 95 and it does have a DOS sound driver. But in my experience, the only games I've ever tried that don't seem to run well from within Windows are usually CGA/EGA stuff. I never have tried a VGA game that failed to work.
Huh. Maybe I'll give it a shot.
Now my problem is finding a way to install Windows 95 when I can't create bootable floppies.
If I burn a Windows 98 boot cd, then use it for format the drive, then swap it for the Windows 95 cd and start the install will I run into any problems?
Didn't Windows 9x come with a boot floppy you're supposed to start the computer up with and then stick the CD in to install it? I seem to recall that XP was the first version of Windows that could boot from the CD itself and didn't require a floppy.
I know that; I have an Acer Pentium III laptop that my boneheaded dad installed Linux on. I'd rather have 98, but I don't have the external floppy that came with the thing so can't install it.
There's a connector on the back for either the floppy or a docking station; not sure which.
>I figure the 75MH 486 is probably too slow for DirectX games.
early ones will work alright on that, i used to run them on a 66mhz 486
most intensive game i ran on it was perhaps grand theft auto (1997), it was quite slow, though
>I seem to recall that XP was the first version of Windows that could boot from the CD itself and didn't require a floppy.
The Me install CD is bootable. I don't remember if the 98 CD is.
Win95 would be more proper, but most games from that era was for DOS anyways. I'd go with a plain DOS install, unless I needed Windows 95 for something specific (or just to restore the machine to its original glory).
This is a 150Mhz laptop with 95 OSR B, although the onboard video can only use 16/32-bit color at 640x480 so you could not run games like Sanitarium that use 800x600 and 16-bit color.
>The Me install CD is bootable. I don't remember if the 98 CD is
It's not. You need the boot floppy for it.
>Win95 would be more proper, but most games from that era was for DOS anyways
Not after 95 came out, they weren't. Devs switched from DOS pretty rapidly.
Tomb Raider required a Pentium 60 if I remember right.
Not sure if that extra 15MHz bump would make it playable.
Need for Speed is only playable at 320x200, at 640x480 it turns into a slideshow.
It's probably better it has it's own thread.
(I know I'm late, I'm just saying - we can have a general retrocomputing thread, then one for a certain guy booting his old system with /g/ "at large" watching him)
This is retrocomputing general, it can be nice for someone to have a retrocomputing specific on some things.
My Me CD is bootable. I just checked.
Pretty much everything I played back then were MS-DOS games, or had an MS-DOS compatible version on the disc. I can only remember Sim Tower being the only Windows title I had. Lots of games released in and around 1997 supported MS-DOS.
What are my options for installing Windows 95? I have the following materials:
The Laptop itself, which has both a floppy drive and a CD-ROM drive, currently running Windows 3.1
Two blank floppy disks
A complete physical copy of Windows NT 4.0 with its Boot floppies and CD-ROM
Modern PCs with CD burners
Can install Windows 95 over NT 4.0?
I fucking love the old Toshiba Satellite look.
I genuinely wish laptops like that were still made. I remember my aunt bought one when she was working in Asia, apparently costing a few thousand HKD.
I think it belongs here, but I'm not saying it belongs only in this thread.
If we can have people talking about their SGI workstations, I think we can have people talking about their NeXT workstations too.
The laptop is running 3.1 currently.
If I install NT 4.0 on it using the media I have, can I then throw in a Windows 95 CD-ROM and install Windows 95, or will I get that old "The version of Windows you are trying to install is older than the one you are currently running" business?
Oh yeah, for most things a post about NeXT systems can go here. I'm just thinking that this thread existing shouldn't be used as an excuse to prevent other, more specific, retro threads also existing. (I'd consider the nostalgia thread to be that, a non-specific nostalgia thread probably more likely to aim at the "I miss the 90s internet" crowd, and the NeXT thread being about one specific guy and his fun with his hardware.)
>I'd consider the nostalgia thread to be that, a non-specific nostalgia thread probably more likely to aim at the "I miss the 90s internet" crowd
If I were a mod, I'd just delete that because nostalgia threads are total cancer.
And you anon, don't you want an S100 bus computer?
I love the way these computers have been designed. It's trully the only architecture where you can turn a 40 years old computer in one of the most powerful micro available.
Here's the problem with that. The basic VGA spec =/= SVGA. VGA as originally created by IBM in 1987 supported the following:
>all CGA and EGA modes+320x200x256, 640x480x2, and 640x480x16
SVGA modes began appearing within only a year of VGA, but there was no standardization in terms of the modes themselves or of the way they were accessed and manipulated. Thus, the VESA standard was established in 1990 to agree on a fixed group of resolutions (640x480 @ 256 colors, 800x600, 1024x768, and 1280x1024). In addition, the memory mapping for them was also more-or-less standardized. That said, there was no standardization on the register mapping for SVGA and every manufacturer used different ones so that cards required their own special driver to use anything more than the BIOS-supported modes.
The VESA committee did also lead to the creation of a BIOS extension that allowed SVGA modes to be invoked from DOS via the BIOS INT 10h function, but this was only at the high level and register mapping continued to be different for every card. Of course it was useless for protected mode applications since they couldn't use the BIOS anyway (unless the video mode was set prior to switching the CPU to protected mode) so separate drivers were still needed for Windows et al.
>SVGA modes began appearing within only a year of VGA, but there was no standardization in terms of the modes themselves or of the way they were accessed and manipulated
A lot of early SVGA cards pre-VESA often did things like use interlaced 1024x768 (thus really 1024x384). These are incompatible with LCD displays.
See, what XP does is just set SVGA modes via the BIOS prior to starting protected mode.
As to why they didn't just do this on Windows 9x, probably to support older hardware that might have possibly not been VESA compliant.
>A lot of early SVGA cards pre-VESA often did things like use interlaced 1024x768 (thus really 1024x384). These are incompatible with LCD displays.
Yup, that's how my 486 machine goes up to 1280*1024, interlacing and all.
You get a performance penalty doing this of course since when SVGA is used in real mode, you can only access 64k of VRAM at a time (via the A000 segment) and have to bank switch the rest. If trying to do it in protected mode, the OS has to also swap data in and out of the first megabyte of RAM, whereas if you have proper protected mode drivers, then you can access a totally linear video buffer.
>You get a performance penalty doing this of course since when SVGA is used in real mode, you can only access 64k of VRAM at a time
This is also what DOS version of games like Tomb Raider that use SVGA modes do. Which why you should just use the Windows version of them if possible. It's running in protected mode with linear VRAM and no 16-bit code, so significant performance boost.