Repaired Basic V4!! YES!!
Moderator: Moderators
- eslapion
- ultimate expander
- Posts: 5458
- Joined: Fri Jun 23, 2006 7:50 pm
- Location: Canada
- Occupation: 8bit addict
Repaired Basic V4!! YES!!
Hi everyone,
Good news! I think I have repaired Basic V4 for the VIC!!!
Back in the 1990's when I gave it to Ward Shrake for his Digital Archeology site he told me that the upper 4k was in fact an image of the lower part.
I compared both halves and sure enough there was ONE different byte.
I fixed this different byte and now all commands appear to work!
I need some beta testers! Please PM me.
Thank you all!
Good news! I think I have repaired Basic V4 for the VIC!!!
Back in the 1990's when I gave it to Ward Shrake for his Digital Archeology site he told me that the upper 4k was in fact an image of the lower part.
I compared both halves and sure enough there was ONE different byte.
I fixed this different byte and now all commands appear to work!
I need some beta testers! Please PM me.
Thank you all!
- Schema
- factor
- Posts: 1430
- Joined: Tue Mar 23, 2004 7:07 am
- Website: http://www.jammingsignal.com
- Location: Toronto, Ontario
- eslapion
- ultimate expander
- Posts: 5458
- Joined: Fri Jun 23, 2006 7:50 pm
- Location: Canada
- Occupation: 8bit addict
It was made by Commodore in 1981 but it was never available commercially. Only a few universities had it.Schema wrote:Can you give us some more background? Who wrote it? Where did it come from? Was it originally commercially available?
It was specifically designed to be a companion to the VIC-1112 interface as this interface uses only the upper half of BLK5.
My copy was recovered from the Université de Montréal in 1982. However, as it was exchanged from hand to hand, a piece of data was corrupted. I gave it to Ward Shrake in 1998.
Using the information from the mirrored image contained in the original file, I was able to restore the data. The file on Zimmer's did not contain the mirrored image.
So why not send the corrected version to Bo so he can replace it? zimmers.net is after all the central repository for Commodore files.The file on Zimmer's did not contain the mirrored image.
Bacon
-------------------------------------------------------
Das rubbernecken Sichtseeren keepen das cotton-pickenen Hands in die Pockets muss; relaxen und watschen die Blinkenlichten.
-------------------------------------------------------
Das rubbernecken Sichtseeren keepen das cotton-pickenen Hands in die Pockets muss; relaxen und watschen die Blinkenlichten.
But is it really a companion to VIC-1112? Although I don't have that particular interface, I tested the broken Basic V4 image with the other type of IEEE interface. As you remember, the Basic extention seemed to address the IEC drive directly rather than via Kernel pointers, so I was able to get a directory from IEC device #8 although the general device #8 was assigned to an IEEE drive at that moment.
Anders Carlsson
eslapion wrote:I just did that.Bacon wrote:So why not send the corrected version to Bo so he can replace it? zimmers.net is after all the central repository for Commodore files.
Bacon
-------------------------------------------------------
Das rubbernecken Sichtseeren keepen das cotton-pickenen Hands in die Pockets muss; relaxen und watschen die Blinkenlichten.
-------------------------------------------------------
Das rubbernecken Sichtseeren keepen das cotton-pickenen Hands in die Pockets muss; relaxen und watschen die Blinkenlichten.
- eslapion
- ultimate expander
- Posts: 5458
- Joined: Fri Jun 23, 2006 7:50 pm
- Location: Canada
- Occupation: 8bit addict
Just reviving this old thread to inform you I sent a .txt file to Zimmer's that contains an explanation of all supplemental commands and registers added by Basic 4.0.
One which may not be explained so well is DS$ which is in fact a read only variable a bit like TI$ but contains the disk drive status. Like @ in JiffyDOS or DOS wedge.
Usage:
PRINT DS$(return)
Here it is...
One which may not be explained so well is DS$ which is in fact a read only variable a bit like TI$ but contains the disk drive status. Like @ in JiffyDOS or DOS wedge.
Usage:
PRINT DS$(return)
Here it is...