descenterace on 28/3/2005 at 20:42
That doesn't tell us anything except 'IE6 is crap' and that's not exactly new information.
My website doesn't display properly in IE6 and it's 100% correct HTML and CSS (or it was last time I checked, anyway).
[edit: Come to think of it, for websites that aren't meant to attract lots of traffic, it's very sensible to ensure that the page doesn't display (either properly or at all; the latter for preference) on IE. It keeps the Unclued away. ]
Crion on 1/4/2005 at 17:31
HUZZAH!
[EDIT]
DOSBOX STILL FUCKING SUCKS
[/EDIT]
[EDIT2]
IMMENSELY
[/EDIT2]
descenterace on 1/4/2005 at 20:42
Don't worry, there's a replacement on the way...
Finished the registers, FPU and opcode maps. Now to sort out the opcodes themselves.
Then I have to add the DOS interrupt services and the DPMI.
Anyone know where I can get the DOS API description for the AWE32?
icemann on 2/4/2005 at 04:35
Crion: It runs Command and Conquer 1 perfect :p.
And atleast through Dosbox we`re actually able to play games on Windows XP that would otherwise be completely unplayable or at best playable without sound.
descenterace on 7/4/2005 at 15:35
w00t!
Update on the DOSBox replacement/elimination project:
I've found a program (and the source for the same) to remove the DOS extender from an application. System Shock 1 decomposes nicely to an LE-format Protected Mode program which can run natively in Windows if a few extra services are provided.
In short, I am now able to write a program that will modify a game's executable file to run natively under Windows. No DOS, no NTVDM, no fiddling with DPMI settings.
The only problem remaining is that of sound and digital joysticks. I can get around this by installing breakpoints at every I/O instruction, but only via Ring-0 access. And guess what? I found some documentation on how to write WinXP kernel-mode drivers! Add call gates to the mix and I can actually set up System Shock 1 (and every other DOS game) to run under Windows XP with sound.
It's not a simple task, though. I'll release a copy as soon as I have the basic loader running. Bear in mind that the 'sound driver' will be KERNEL-MODE, so when I do get it working consider carefully that it will have unrestricted access to every little corner of the OS. When invoked. I plan to leave it installed as a general service which is invoked by the aforementioned replacement loader, so it should be safe.
Enchantermon on 7/4/2005 at 18:17
Quote Posted by descenterace
Add call gates to the mix and I can actually set up System Shock 1 (and every other DOS game) to run under Windows XP
with sound.
:wot:
I like where this is going..... :cheeky:
Enchantermon
ToxicFrog on 7/4/2005 at 19:01
@descenterace: if you can get this working you are a god. Also, source please.
(Isn't it PE format, not LE?)
NHJ BV on 7/4/2005 at 20:08
I already have SS1 working with sound on WinXP, but I like where this is going :)
Shadowcat on 7/4/2005 at 21:52
Quote Posted by descenterace
In short, I am now able to write a program that will modify a game's executable file to run natively under Windows. No DOS, no NTVDM, no fiddling with DPMI settings.
Holy cow! Outstanding!!!
(
w00t! indeed...)
descenterace on 8/4/2005 at 00:11
PE is the Windows EXE format. MZ is the old-style DOS format. Somewhere in between are the LE, LX and LC formats, which contain native 32-bit code that requires Protected Mode. These formats typically require a DOS extender such as DOS/16M or DOS/4GW to load them and provide the necessary interfaces. An LE, LZ or LC file is not actually executable unless wrapped in an extender, which will appear (to DOS) to be an MZ file.
After a little more research, I have determined that this project is very possible. In fact, this little utility should eventually work with any DOS-extended game. I have source for the unwrapper. I have source for the LC loader. I have source for WinXP kernel-mode device drivers.
And I have a huge-ass Pentium CPU manual, detailing the exact workings of Protected Mode...
And finally, I don't have any exams until the last week of May.
