Just one note: tell me, if Xemu/C65's implementation behaves incorrectly. it just interprets things, I've written here already, I am not sure if it's 100% identical to a real C65 (or MEGA65, or - in fact - MEGA65 follows C65 here 100% correctly ... that's the reason I delayed this drive LED emulation to go into Xemu/MEGA65 and I started with Xemu/C65 only as a kind of "test")
Finding and reconstructing a C65 ROM
- Snoopy
- Thread is Unresolved
-
-
Ubik:
Actually, it blinks for the fraction of a second in C65 mode. My guess is that the C65 Kernal reads the error channel after accessing DOS (thus ending the blink state) while the C64 Kernal leaves it alone..
As far as I can overlook, it was intended by Commodore for the C65 (mode) exactly this way, in contrast to the C64 (mode). After the error message has been output, the LED should switch off again.
Hmm, maybe makes sense, in the old C64 days user could not see the error message, thus there is the blinking light to show. But if the error is actually displayed, user can see it. And indeed, I can see in Xemu that actually blink is set for a brief moment, but maybe switched off by reading the error msg. Of course just guessing, I thought this is behaviour is actually a problem, but thinking the Snoopy-way
it makes some sense at least.There's an additional information about the drive LED handling in the C65 ROM, in the document: C64DX_aka_C65_System_Specifications_Preliminary_(1991_Mar).pdf
The page below is page 331 of 332 in the document.
The information is found in the second last paragraph:
The whole document can be found here: http://www.zimmers.net/anonftp…reliminary_(1991_Mar).pdf
-
-
Just for info:
Yesterday I received a mail from someone who is not in the forum with a "C65-JAR.SFX" file.
Unfortunately, according to him, the file also comes from a large pool of files that have "sometime" been downloaded "from somewhere". Therefore it is unfortunately not possible to find out more about the actual origin here either.
I've tried this file, but unfortunately it has the same error. A binary comparison of both files has shown that they are exactly the same. Probably only the file with the defective file "65r6dmp3" is on the internet from this image.
But many thanks for the help! Every info and hint will be still very welcome and helpful!
-
Looking through the ROM today, it seems to me that on the BASIC 10 command has been worked on, but I am not getting it to work properly yet.
SAVEIFF "filename" saves a file with the specified name, but the content is much too short for an IFF and doesn't necessarily look like an IFF to me.
It seems that the command implementation is not being finished ...
-
I took the liberty of accessing the technical forum knowledge on this question:
Thanks to great help, there were some hints in this thread that the ROM or the floppy disk could come from Dennis Jarvis.
At least that's a first hint!
-
unfortunately, as far as i know, Dennis Jarvis passed away. if my research is correct it must have been 2016.
But like Snoopy already mentined, it seems like, Dennis Jarvis made most of the C65 data public after the project was canned.
-
unfortunately, as far as i know, Dennis Jarvis passed away. if my research is correct it must have been 2016.
Oh, I didn't know that!
But like Snoopy already mentined, it seems like, Dennis Jarvis made most of the C65 data public after the project was canned.
Yes, Dennis Jarvis gave many discs away for being archived and published:
In early 2012 I was contacted by Dennis Jarvis. He was a software engineer at Commodore,
working on software for various disk drives and computers, including the 1581 and the fabled C65.
He was also involved in other projects as well as co-writing a book about BASIC 7 on the C128.
Dennis asked me if I could archive some of his old disks, and also sent me a few interesting pieces
of hardware that were used in development. On this page I present some pictures and
disk images. Dennis sent me many disks, both 5.25" and 3.5" in different formats.
These disk images are straight dumps of the disks, and are presented as-is here for your enjoyment. -
Hmm, maybe we should update the C65 Wiki Page
-
Yes, we should update the C65 page on the C64 wiki.
LG
Paul
-
Hi @all,
after we have been able to read on how Snoopy reconstructed the 911210 ROM, i would like to point you now to another teammembers
guestpost at Paul's blog. I believe it fits into this thread
Bit Shifter took the time to write a nice insight into the process on how he started to pick up the work on the ROM where Commodore left,
to transfer it to the 21st century.
please have a read and enjoy
