There were a few issues in that firmware release, the first was the reply to the SCSI scan inquiry. I respond with a 32byte string which satisifes Windows but gave linux a hard time as it was expecting 36 bytes. This is purely a device serial number so V1.01 fixed that by adding a few bytes.

Next is the 570mb storage size. This came about because the BennBenn cart > 8mbytes and fat12 can only index a limited drive size. Technically, 570mb in fat12 can not work with a standard cluster size. I increased the cluster size which made all the numbers come together to form 570mb which by the spec was legit and windows had no problem with it. Linux did. I've pushed the drive size back down to the original Fat12 spec and now linux is happy.

The input/output error was due to Linux trying to address a cluster which was simply not there. It couldn't comprehend the larger than usual cluster size (decided to ignore the byte in the MBR) so assumed a standard cluster size which exceeded the 12bit address FAT12 uses.

The latest version, v1.02 includes all these fixes but still doesn't satisfy Win8.1's implementation of Fat12. I've been told by a few customers that if they use a 3rd party app that doesn't call on the OS's Fat12 drivers there is no problem. An example was using GBcameraDump program to read/write the .sav file.

If you PM me your email address I'll forward you the latest firmware now

Bus 002 Device 054: ID 1908:0102 GEMBIRD
1229731.610554] usb 2-1.4: reset full-speed USB device number 54 using ehci-pci
[1229731.708093] usb-storage 2-1.4:1.0: USB Mass Storage device detected
[1229731.708228] scsi host12: usb-storage 2-1.4:1.0
[1229732.711227] scsi 12:0:0:0: scsi scan: INQUIRY result too short (32), using 36
[1229732.711235] scsi 12:0:0:0: Direct-Access     BennVenn 's Joey-Squinson  v1  PQ: 0 ANSI: 2
[1229732.717099] sd 12:0:0:0: [sde] 1114112 512-byte logical blocks: (570 MB/544 MiB)
[1229732.717817] sd 12:0:0:0: [sde] Write Protect is off
[1229732.717821] sd 12:0:0:0: [sde] Mode Sense: 55 53 42 43
[1229732.718449] sd 12:0:0:0: [sde] Incomplete mode parameter data
[1229732.718455] sd 12:0:0:0: [sde] Assuming drive cache: write through
[1229732.727951]  sde:
[1229732.730319] sd 12:0:0:0: [sde] Attached SCSI removable disk

I get one partition:
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                               
Model: BennVenn 's Joey-Squinson (scsi)
Disk /dev/sdf: 570MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number  Start  End    Size   File system  Flags
1      0.00B  570MB  570MB  fat16

(parted) 

When I try to mount it:

sudo mount /dev/sdf  -o ro -t vfat /tmp/tttt
[eric@pc GB303]$ ls /tmp/tttt
ls: cannot access /tmp/tttt/?�o?.=?o: Input/output error
ls: cannot access /tmp/tttt/?�_?.N?o: Input/output error
ls: cannot access /tmp/tttt/
?`
h?: Input/output error
ls: cannot access /tmp/tttt/
?.�??: Input/output error
ls: cannot access /tmp/tttt/?�m(hm.�B: Input/output error
ls: cannot access /tmp/tttt/?N?M?L�.: Input/output error
ls: cannot access /tmp/tttt/��.

...
Using windows in a VirtualBox, everything is working fine.
The capacity seem to be 8MB (which seems correct), not 570MB
Under the USB device , I can find:
USBSTOR\DISK&VEN_BENNVENN&PROD_'S_JOEY-SQUINSON&REV__V1\6&A1F30D8&0

VirtualBox sees the device as "bennvenn usb linker v1.0"

If you dig into device manager in windows and bring up the info on the USB device it will tell you the software version number (v1.00 - v1.02 etc...)

PM me your order number and I'll email you the latest firmware

My latest revision (v1.02Yosemite) works fine on my Ubuntu OS and my laptops Lubuntu OS. What version are you running?

Humm, sorry I don't know. How can I find my current version? Can you please also tell me where I can update it, if it is outdated?
Thanks

Spent 8hrs yesterday trying to install 8.1, seems my bios isn't compatible. Ended up with windows 8 on the laptop instead which works fine with my Gen2 stuff but unfortunately I can't replicate this windows 8.1 file system problem. Yet...

No worries, will PM now.

I'm still waiting on an EMS32 cart to arrive so I can add support. I expect it will freeze and throw an error if you try write to it. The erase block size is different so only every second block will erase and be written.

I can blindly code support for your ems32 and you can give feedback, or when my EMS32 eventually arrives I'll have a stable firmware update for it.

Please pm me your email and I'll send you the latest osx firmware

Admittedly, I tried overwriting the existing file rather than deleting it first, so maybe that was my problem. It seemed to work but then when I ejected it and added it again the file was 0 bytes.

Strangely though, after ejecting again and leaving it for a while it seemed to work properly in my DMG (and displays as the correct size in Explorer), so I guess I'll just leave it as it is for the time being. Any ideas? Did I get a dodgy unit, or am I not supposed to be using it with the old EMS carts?