einSDein troubleshooting

[vanpeebles]

I'll try and move all the posts into here

[vanpeebles]

On my second Tatung, I get identical photos to what Lardo got. But, it worked first time, and only once. Even a ctrl break stopped it working. Could it be doing something to the sd cards?

How do you image your sd cards and what settings? Fat 16/32, file allocation blocks etc?

I think it's 1.21 (first machine has 1.2, second 1.21) on both machines. Tried your sd rom without and with window on first tatung. Second Tatung was the black sticker sd rom.

[sirmorris]

I wondered if the sd card was being corrupted. Can you check the config.ini file and see what drives are mounted? Do the configuration options point to valid files on the sd card??

All the FATs should work, I use a 16gb card at home which I think is FAT32.

[vanpeebles]

I could try zipping the files to send to you?

[Lardo Boffin]

Here is my Config.ini:-

965C8AE5-4438-4E31-A37E-97FA1FC707B9.jpeg (361.64 KiB) Viewed 17232 times

The file and folder it points to is present.

[vanpeebles]

default2=DSK/ZORK1.DSK
default3=DSK/DEFAULT3.DSK
bootimg=BOOT.BIN
dosimg=DOS250.BIN
flags=0x80

That's from the time I got it working and managed to set up zork1.dsk on drive 2.

the three files from the boot card attached

[sirmorris]

Hmm that looks fine. @lardo - can you open file in wordpad to see if the carriage returns are present? I'm sure they are but nopepad makes a hash of non-windows line endings.

[vanpeebles]

Do you set up your SD cards in linux or with a program??

[Lardo Boffin]

Hmm that looks fine. @lardo - can you open file in wordpad to see if the carriage returns are present? I'm sure they are but nopepad makes a hash of non-windows line endings.

Carriage returns look fine.

C246F1CD-8FF5-4162-B61E-8B06CA874E9D.jpeg (80.22 KiB) Viewed 17222 times

[sirmorris]

I can't say I've formatted many SD cards, I generally just erase all the files on them. If I do run a formatter it's the SD association one that everyone recommends.

It's weird that you both have the same symptoms. It could just be coincidence - there were other einSDeins out in the wild with no issues and I'm wondering if it's a systematic issue relating to the hardware in these machines? Like if they are different revisions or something. The only way I can tell however is if I get the machines on my bench for some deeper investigations. einSDein can output debugging info, but it needs a serial connection to the board.

I'm without an einSDein at the moment, so I'll build one quickly and try some things out.