Home Page Forums MAME MAME 8bit Apples - Apple I, II, /// and the 16 bit GS

Oh, yeah, if they're dumped or whatever.

Of course, at the moment I'm looking at BeebScan which is a handheld scanner for the BBC. The same scanner was also used with the Archimedes, see http://chrisacorns.computinghistory.org.uk/32bit_UpgradesH2Z/WE_SCannerIF.html. The scanner is read-only and continually outputs a stream of bytes of the current line in view, when the button is pressed. As this is a generic scanner, used with many other machines at the time, it came with an interface board for the relevant micro.

On Windows there is WIA which can connect to scanners, digital cameras etc. I'm sure on Linux there is something similar (maybe SANE?).

I guess what rfka01 is asking is, would it be possible to add such support to the OSD layer for those kind of scanner devices?

Something something send PR

Eh? I thought his clarification was that he was talking about emulating hand scanners using e.g. the picture image device, not actually supporting them for input.

I'd like to emulate the Cauzin Softstrip reader for giggles - we have enough old magazine scans to make it worthwhile.

I mangled up two ideas in my posts before: One thing was taking snaps with a USB connected webcam instead of supplying PNG graphics to the emulated scanner. The other thing was emulating a hand scanner within MAME. Pernod and RB got it right.

Nah, I better leave that to someone who actually cares about that feature. I was just pointing out that there *is* an API for scanners, at least on Windows.

But I misunderstood rfka01 so it doesn't matter anyways ;-)

More fiddling with the Apple /// driver: There's some major weirdness with Business Basic and using the mame debugger.

It seems that there's a strange interaction when the debugger is active. If I type in the simplest of basic programs:

100 GOTO 100
RUN

It will run fine with no debugger.

With the debugger active, it seems that the more debugger windows I open (I think at least a couple of memory windows) will cause the running program to either drop out to a command prompt or get a ?SYNTAX ERROR IN 100 error. Sometimes it takes a while for it to happen.

./mame64 apple3 -flop1 Apple3BusBasic1.23.dsk -console -window -debug

That means some read-activated softswitch doesn't have a debugger guard on it, although everything in the /// should.

Hi RB,

I looked at apple3_memory_r and it looked like it guarded most things, perhaps it is getting confused with the fetching of the xbyte causing side effects by changing m_indir_bank?

(I probably don't know what I'm talking about since I'm new to apple 3 stuff)