VOGONS

Search

Common searches

Search results

Display options

Display options

Re: Fastest DOS VLB Graphics card ever?

Posted on 2017-10-23, 13:49

its my most prized possession and most favorite game of all time that re-defined 3D gaming. I play Duke Nukem 3D now and then, also have Warcraft 1/2 + Expansion pack. I have over 36 games for the system including Links 386 with pretty much every single golf course add-on I was able to find. Just …

Re: test386.asm CPU tester

Posted on 2017-10-23, 13:42

Looking at the 0xEE output, the last line starts with "IMUL32 D EAX=FFFFFFFF EDX=FFFFFFFF PS=0000", which only appears once in the reference file. So the problem happens after returning from logging, but before the "DIVDL B EAX=00000000 EDX=00000000 PS=0000 #DE EAX=00000000 EDX=00000000 PS=0000" …

Re: test386.asm CPU tester

Posted on 2017-10-22, 20:01

superfury wrote: This is POST EE currently executing(hanging?), possible invalid code: debugger_UniPCemu_20171022_1757.zip Can anyone see what's going wrong? I can't seem to find the executed code anywhere in the asm files? Can't say by reading the log. Can you post your lst file and the ROM output …

Re: test386.asm CPU tester

Posted on 2017-10-20, 20:26

Bochs 0xE9 hack port More information about this E9 hack extension can be found at: https://bitbucket.org/superfury/unipcemu/wiki/Debugging Interesting. I'll definitely consider this. So perhaps an option for 486-specific tests, defaulting to 386 compatibility? Yes, a configurable equ to enable CPU …

Re: test386.asm CPU tester

Posted on 2017-10-20, 20:15

Note that ARPL won't write to memory unless it has to alter the value. If the page were write-protected, it would be a test against always-write (cmpxchg does the same). That would be a good test. I broke QEMU many years ago like that. I'll add this to the tests! I opened an issue rather than …

Re: Common log format

Posted on 2017-10-17, 20:21

superfury wrote: What about instructions that might have a memory operand only DOSBox's disassembler specifies the size before the operand, for example: Copy code to clipboard 1 push word cs:[bp+01] 2 cmp byte [0030],00

Re: test386.asm CPU tester

Posted on 2017-10-17, 17:24

It seems like you have an old version of the src/test386.asm file. I've added the POST 0 macro only recently, after you noticed that it wasn't emitting a 00h diagnostic code for the first test. Here's mine so you can compare. Filename test386.lst.zip File size 60.72 KiB Downloads 92 downloads

Re: test386.asm CPU tester

Posted on 2017-10-17, 16:54

Edit: It also doesn't seem the POST macro is being assembled, it resolves to no code being inserted? The conditional jump tests start immediately after CLI, the code "POST 0" isn't being assembled at all? Can you upload your intermediate assembler source-listing file? This can be generated by NASM …

Re: Common log format

Posted on 2017-10-16, 18:07

Do you have a diff or code that I can apply to bochs' source code to have that instrumentation plugin? I can work on changing it to match the new common log format. bochs-instrument.zip Place the code inside the Bochs' intrument folder and follow the instructions inside instrumentations.txt to …

Re: Common log format

Posted on 2017-10-16, 16:14

@hottobar: I like that format, except for the empty spaces. When we are dumping millions of instructions that can easily double the log size for no actual useful reason. We should just print the instruction bytes followed by space then instruction decoding. Compact is important. I decided in favor …

Re: test386.asm CPU tester

Posted on 2017-10-16, 16:05

vladstamate wrote: it already showed issues, so I am fixing stuff now. Happy to hear! This tool helped me to fix many bugs as well. I hope some day it'll be able to test much more because my CPU still has some problems that this program is not able to detect.

Re: Common log format

Posted on 2017-10-15, 19:10

Question though. You seem to have a mix of single spaces and double spaces. Can we make it all single space? It makes much easier to parse: 0028:800073B5 8D 14 9A lea edx,[edx+ebx*4] Sorry, I mangled spacing when pasting the log entry. Actually my current format is the following (in sprintf format …

Re: test386.asm CPU tester

Posted on 2017-10-15, 14:26

@superfury answering your questions from the other thread, the SDL crash is definitely not related to test386.asm, which doesn't even use the video output. The COM port is not mandatory and can be disabled. The LPT port is only used by writing ASCII bytes to 3BCh (unless you changed the address); …

Re: Common log format

Posted on 2017-10-15, 13:54

You can limit the address space of logged instructions, but many interrupt handlers are DOS programs below the 0xa0000 limit. For addresses I'm currently using the DosBox approach so, for example, this is a typical log entry for me: 0028:800073B5 8D 14 9A lea edx,[edx+ebx*4] So , is the value of CS …

test386.asm CPU tester

Posted on 2017-10-15, 13:37

Debugging an emulated CPU can be the most frustrating debugging experience ever, with so many moving pieces that can interfere with the instructions flow. You'll end reading huge trace logs with millions of executed instructions in the hope of finding that damn bug that keeps Windows from booting. …

Page 2 of 3

Go to top of page Go to top of page
Close window
Close window