Page 1 of 4

EightyOne 1.0

Posted: Sun May 11, 2008 6:19 pm
by Mike
As some people may not be aware, there is a new version (1.0) of EightyOne at http://www.chuntey.com/

The website isn't there atm, but I'm hoping to do something with it soon.

My email isn't set up at the moment, so if there's any bugs (ha!) pm me here.

Mike

Re: EightyOne 1.0

Posted: Mon May 12, 2008 12:19 am
by BrunoFlorindo
Thank you Mike.
Here are some of the thinks that I really like about EightyOne:

-TV emulation
-Number of clones emulated
-Number of peripherals emulated

A few things that might be useful in the near future:

-Option to load from audio source. I'm testing many TS1000 tapes and it would make the job a lot easier, especially for preservation purposes.
-To share with us how you were able to emulate so many peripherals. It seems it's almost impossible to find information on some of them. :)

P.S. The other day I was checking some of your older pages (using www.archive.org) and I was impressed with your SP81 project. Really nice work.

Re: EightyOne 1.0

Posted: Mon May 12, 2008 10:40 am
by XavSnap
I'm happy to read you, Mike !

Many Thanks.

XavSnap : EO tester.

Re: EightyOne 1.0

Posted: Mon May 12, 2008 11:03 am
by sirmorris
I'm working with - or should that be pestering ;) - Mike with the aim of improving EO's debugging facilities.

I'm hoping to implement some or all of the following:
memory display with changed byte highlighting
structure dereferencing
expanded flag register display - show names and allow toggling
improved register display, allowing changing of values more easily
option to always/never step over calls / inc&repeat instructions
fix some of the disassembler errors with long instruction decoding
import of tasm symbols for disassembly
breakpoint manager
If anyone has any suggestions I'll be happy to listen.

C

Re: EightyOne 1.0

Posted: Mon May 12, 2008 1:58 pm
by Andy Rea
Firstly A big thanks to Mike for EightyOne, it's a great emulator tha i almost always use for ZX81 tasks,
sirmorris wrote:I'm working with - or should that be pestering ;) - Mike with the aim of improving EO's debugging facilities.

I'm hoping to implement some or all of the following:

memory display with changed byte highlighting
This is one of those features that i really wanted, and prompted me to have a go at my own ZX81 emulator.
improved register display, allowing changing of values more easily
This would be a great feature.
fix some of the disassembler errors with long instruction decoding
i had already noticed this little bug. Another little bug with the keyboard mapping over on the numeric pad '/' and ' * ' are swapped, '-' works without shift '+' only works with shift.

i would like to see an extended disassembly listing showing past instructions also, many times i have forgot to turn on the history and wanted to look bak a few instruction, in my implementation i show 8 past, 1 current (excuted on next step), 8 future (which may change, e.g current been a call).

Great work Mike kepp it up.

Regards Andy

Re: EightyOne 1.0

Posted: Mon May 12, 2008 2:08 pm
by sirmorris
I imagine that I'll try and keep the presentation separate from the implementation, so perhaps my code could be re-used. I'll be happy to bear that in mind.

Bugg report in FAT.TXT !!!

Posted: Mon May 12, 2008 3:01 pm
by XavSnap
XavSnap to XavSnap: " Bugg report in FAT.TXT !!! "
recieved in my mail box...

XavSnap: "Dear XavSnap,
I allways use your emulator, and it seem to be the best and more reliable."
Me: ":: Cool ! ::"
XavSnap: "Eighty-One is the best emolator on the web!"
Me: ":: Ooops! ::"
XavSnap: "But..."
Me: ":: Yheea ! ::"
XavSnap: "I can't use the IDE hard drive..."
Me: ":: Gloops!!! ::"
XavSnap: "I'm an anomimous fan!"

Me: ":: ??? :::"

"Dear XavSnap,

If you want to use this feature, you had to read the FAT.txt file...
But you had to follow there steps:
1- You had to select the hardware Window, select "Zx81".
2- Clic on the drives tab end select "Mwcfide"
3- Select 32kb of memory.
4- In 'File', select 'Drives' (in the first text-box...) to mount the virtual disk (FATTEST.VHD in the EO directory)
5- in 'File', select 'Load Memory Bloc', select the 'MwcfIDE.Rom' file and Type-in '32768' (8000h) in the 'Offset' text-box.
6- Then type 'RAND USR 32768' at prompt. ('T'+ (shift + enter)+'L'+'32768'+'Enter')
7- Type "A:"
8- Type "DIR"
9- End read the 'Fat.TXT'.

It work very well.

Thanks very many much XavSnap.
Regards."

Sorry Mike! i can find any problems !
Have Fun.

Harrg! YES !!!

"1) byte sequence FD 36 3B 40, disassembles as LD (IY+$40),$3B, It should of
course be LD (IY+$3B),$40
2) 2 byte operands are reversed. i.e the byte sequence in rom at $0002 01
FF 7F LD BC,$7FFF is shown as $0002 01 7F FF LD BC,$7FFF
This may be by design to make it easier to read."

Thank you very much Andy !
EO isn't too many the best!!! two buggs (2) (II) (ONE+ONE) !!!

NB: Sorry! my "Sinclair ZX81 Basic" is ... is better!

Re: EightyOne 1.0

Posted: Mon May 12, 2008 3:11 pm
by sirmorris
Xav - the medication is on its way ;)

Re: EightyOne 1.0

Posted: Mon May 12, 2008 5:06 pm
by Andy Rea
Forgot to mention in my previous post a feature i would like, The effects of the next instruction on the registers with altered registers highlighted (perhaps switch off-able, i get confused as to which set i'm supposed to be looking at)

And 1 more which i thought about in the meantime and would only be of value if a) you could modify registers, b) and or modify memory contents. A Rewind facility allowing one to backup code (1 instruction at a time), of course having the registers/memory/anything else (that i forgot) back in the state it was. This i imagine would require lots of extra memory to allow infinate backup's so perhaps it should be limited to 16 or 32 steps. My initial thoughts on how to possibly inplement this would be some kind of rolling journal of past states (but not the complete memory state, just the relavant changes)

regards Andy

Re: EightyOne 1.0

Posted: Mon May 12, 2008 5:33 pm
by Mike
I'll leave sirmoris to sort out the debugger. Ah, the power of deligation :)

Regarding the keyboard mapping, I'll fix that asap. The problem stems from the fact that EightyOne has been developed entirely on a laptop - hence the numeric keypad functions have never really been tested by myself.

Mike

[edit]

Hmmm. Just tested the numeric keypad and it works fine here. Everything as it should...