Yeh I'd assume this would be possible, install a custom interrupt handler on the illegal opcode exception, detect the opcode and run it in software. If they'd use lot's of pentium instructions afterwards it would be dog slow though 😀

It would be interesting to see something like this for SSE2 instructions, especially on an Athlon XP or Pentium III system.

mr_bigmouth_502 wrote:

It would be interesting to see something like this for SSE2 instructions, especially on an Athlon XP or Pentium III system.

+1 😀
I will be more than happy to chip in with contributions(to my best) and ready to dust up my programming skills, if an expert jumps on the bandwagon.

I think this is a clever idea but I suspect it wouldn't be easy to do!

I know something about programming but not driver development. Otherwise I would be working on it right now

Yeh I'd assume this would be possible, install a custom interrupt handler on the illegal opcode exception, detect the opcode and run it in software. If they'd use lot's of pentium instructions afterwards it would be dog slow though 😀

But there are some programs that use just enough P5+ instructions to not work. It shouldn't impact those too much.

It would be interesting to see something like this for SSE2 instructions, especially on an Athlon XP or Pentium III system.

Once the framework is in place, it should be possible to emulate almost any instruction

I observed the most common faulting instructions seems to be rdtsc. I wonder why it is used so much?

It's a nice high resolution timer.

Not the most stable though. I kind of wish rdtsc was never made.

Anyway, I found some code to work with https://web.archive.org/web/20090727072648/ht … .com/dalex_257/

It really isn't that complicated. I just need to find a way to compile it (and a windows ddk I guess)

here is a article called "How to use the Invalid Opcode Exception interrupt" with assembler code example.
http://mtech.dk/thomsen/program/ioe.php
Maybe it is of use.
(I need to convert this to DJGPP for my own project...)

Some progress. I confirmed the binary driver on that page installs on Win2K atleast on my 486 without crashing.
I am now in the progress of installing the MS DDK. See how that goes

I need help.
This is the initial test handler. Keeping it simple, all its suppose to do is skip CPUID

The problem is I cannot figure out how to return to execution past the illegal instruction.

I run a test program that executes CPUID and trying different things either the program crashes
or the whole OS BSoDs

1__declspec(naked) void illegal_operand_handler (void) { 
2    __asm{
3        push    ebp
4        mov     ebp, esp
5        pushad
6        pushfd
7        push    ds
8        mov     ds, ax
9        mov     esi, [ebp+4]
10        cld
11        lods    byte ptr [esi]
12    	cmp     al, 0xf  
13		je      handle_0xf
14GoPrevTrap01:
15        pop     ds
16        popfd
17        popad
18        pop     ebp  
19        jmp     dword ptr [prevIllegalOpHandler]
20        
21handle_0xf:
22		lods	byte ptr [esi] //Find out what the faulting instruction is
23		cmp		al, 0xA2
24  		jne		not_cpuid 	
25		add     dword ptr [ebp+3], 4
26        pop     ds
27        popfd
28        popad
29        pop     ebp
30        iretd		
31not_cpuid:
32		jmp short GoPrevTrap01
33    }; 
34} 

Dear All,

Dosbox.exe does not support running a third party exe with arguments.
May someone let me know how to use exe with arguments in Dosbox.

Also, When i tried to debug the source code of dosbox application that i downloaded from the below site has 343 errors. some of the errors for reference.

http://www.dosbox.com/wiki/Building_DOSBox_wi … _C_2008_Express

1.error C2143: syntax error : missing ';' before '*' sdlmain.cpp
2.error C3861: 'SDL_WM_SetCaption': identifier not found sdlmain.cpp
3.error C4430: missing type specifier - int assumed. Note: C++ does not support default-int sdlmain.cpp
4.error C2039: 'overlay' : is not a member of 'SDL_Block' sdlmain.cpp

Thanks
Deepika

Deepika wrote:

Dear All, […]
Show full quote

Dear All,

Dosbox.exe does not support running a third party exe with arguments.
May someone let me know how to use exe with arguments in Dosbox.

Also, When i tried to debug the source code of dosbox application that i downloaded from the below site has 343 errors. some of the errors for reference.

http://www.dosbox.com/wiki/Building_DOSBox_wi … _C_2008_Express

1.error C2143: syntax error : missing ';' before '*' sdlmain.cpp
2.error C3861: 'SDL_WM_SetCaption': identifier not found sdlmain.cpp
3.error C4430: missing type specifier - int assumed. Note: C++ does not support default-int sdlmain.cpp
4.error C2039: 'overlay' : is not a member of 'SDL_Block' sdlmain.cpp

Thanks
Deepika

You should start a new thread rather than replying to an unrelated thread.

You may notice all those errors relate to sdlmain.cpp. This suggests that you may not have the SDL libraries installed correctly.

The only way to start an executable within DOSBox via command-line arguments when DOSBox is started is to use multiple instances of the "-c" switch to mount the appropriate directories and launch the appropriate executable.

smeezekitty wrote:

I observed the most common faulting instructions seems to be rdtsc. I wonder why it is used so much?

RDTSC is sampled twice to measure the actual CPU speed in MHz. Though multi-core and speedstep configurations now complicate this process.

Ok progress.
It is now able to skip certain bad instructions

Working on emulation now.

BUMP!

I know this is an older post, but I have been for looking ages for an SSE2 driver that would emulate SSE2 instructions on WinXP so small or simple programs that require it can run on older computers.

Was progress ever made here?

Gypsum Thirty wrote:

BUMP!

I know this is an older post, but I have been for looking ages for an SSE2 driver that would emulate SSE2 instructions on WinXP so small or simple programs that require it can run on older computers.

Was progress ever made here?

SSE3 is pretty complicated. IIRC, I was able to catch and handle missing instructions. But my ISR skills were lacking to implement things like rdtsc