Denial

Ok, found the problem in sd2iec: http://s1.postimage.org/yyPiA.jpg The A marker in that picture is the point where the VIC20 sets the ATN line to low. Usually the CLOCK line is also set low at this point or slightly before, but for some reason (I'm currently too lazy to read the rom listing of the c...

However I was still gonna try this with a true Commodore IEC drive before contacting you directly to make sure it's really a bug in SD2IEC and not to waste your time otherwise ;-) I just tried it both on a real machine with a OC118 (small, quiet, convenient ;) ) and in xvic with TDE enabled - fails...

tokra wrote:Upon further looking I now have found your contact in the README-file of the SD2IEC-firmware.

I know, nobody reads the README...

I appreciate all the hard work in SD2IEC and also the new GEOS driver for it!

I'm starting to hate Wheels.

I suppose it's an incompatibility of the SD2IEC-software that doesn't work correctly with sequential file reading using GET# and such. Hint: I usually don't fix bugs that I don't know about, so if people just complain about problems on random forums instead of sending me a mail those problems usual...

fsporsche wrote:with a plus feature of a SD/Card reader built in.

Yet another sd2iec-based hardware?

Vic20-Ian wrote:an SD card reader that emulates floppy drive and accesses up to 2GB.

16GB cards are confirmed to work, in theory 32GB should work too (way too expensive to just buy one for testing)

Diddl wrote:Since this would be a SD2IEC problem it should concern µIEC also and all american SD2IEC user (NKC customer).

Why would it be an sd2iec problem?

Btw by using the 512MB card from uIEC, I've noticed a strange 65535 DEL file Interesting... In theory the readdir for FAT should not be able to generate DEL entries at all and looking at the code I can't spot any missed execution path that would result in a DEL entry. Was it starred (*DEL) and/or l...

Maybe that it is the correct behaviour since now there should be a newer firmare (0.9.1) and in this case I need to wait a 0.9.2 version but there is an "emergency" firmware that will be always flashed from any version ? That hypothesis is correct, the bootloader won't "up"grade...

Normally there is no need to update to 0.9x, cause most changes are only REL files concerned. Sure, if you like broken swap lists you can stay on 0.9.0... FE3 has a normal SD2IEC hardware, so it is no problem of FE3 but from SD2IEC firmware maybe. Hope it is solved at 0.9.2 The only influence sd2ie...

Pedro Lambrini wrote:The power light for the uIEC comes on and the green light does it's wee on-then-off thing but when I did a LOAD"$",8 all I get is the DEVICE NOT PRESENT error! Why wouldn't this work? Any ideas?

Check your connections once more, you probably swapped some of the signal lines.

Vic20-Ian wrote:How does SID set its registers?

The SID registers are mapped into the CPU's address space and can be written by writing something to the address where they're mapped to.

e.g. Could I send escape codes as a serial pulse on one pin of the expansion bus?

No

OK thanks Unseen - but the problem is: once you load the Z-machine, you can't exit to BASIC, but you have to swap disks and load the story disk from the Z-Loader menu. This is the problem with Infocom adventures on *.d64. :cry: Now guess why the firmware supports two "disk change" buttons...

carlsson wrote:TNT has written his own Z-machine interpreter which runs on PET, VIC-20 and so on.

Oh, neat.

In that case you could just send "CD_" (left arrow) and "CD:<name_of_disk2.d64>" to the drive, the button does basically the same but with less choice which file to change into.

Beacuse Infocom games don't usually have enough space for save files on data disk, and I guess most FE3 owners have not installed disk change buttons. The Infocom interpreter has a function to send arbitrary commands to the drive? I don't remember anything like that in the original manuals. Unless ...