Steve Nickolas

http://i.imgur.com/uMH8M.png

This is my latest work in progress.

I wonder what's missing that makes it blow up like this...

Maybe because the drive emulation is sloppy? (it's the old Dapple code
running in turbo mode.)

-uso.

Steve Nickolas

Replying to myself with more info. Also moving it to cea2 which might be
more apropos.

http://xtra.usotsuki.info/daplus3-000.zip

OK, the problem is reproduceable in Apple ][ "emulation". It affects
ProDOS as well (only 1.0 or 1.0.1 would even work on this configuration).
Some other software also exhibits weird behavior that I can't seem to
explain.

When apple3.rom is present, daplus3 attempts to emulate an Apple ///. You
might need to hit Ctrl-F12 a couple times during the POST to get it to
boot. Ctrl-Alt-F12 pulls up the monitor (I believe this is like a real
///).

When not present, it expects to find a SOS.INTERP#090000. This is the
same file which can be found on the included disk image, and contains the
Apple ][ emulation module "Star Emulator" that I threw together about a
year and a half ago.

Emulation is spotty as hell.

-uso.

Bill Garber

"Steve Nickolas" <lyricalnanoha@usotsuki.hoshinet.org> wrote in message news:alpine.DEB.2.00.1112270401360.18789@ns383864. ovh.net...
> Replying to myself with more info. Also moving it to cea2 which might be
> more apropos.
>
> http://xtra.usotsuki.info/daplus3-000.zip
>
> OK, the problem is reproduceable in Apple ][ "emulation". It affects
> ProDOS as well (only 1.0 or 1.0.1 would even work on this configuration).
> Some other software also exhibits weird behavior that I can't seem to
> explain.
>
> When apple3.rom is present, daplus3 attempts to emulate an Apple ///. You
> might need to hit Ctrl-F12 a couple times during the POST to get it to
> boot. Ctrl-Alt-F12 pulls up the monitor (I believe this is like a real
> ///).
>
> When not present, it expects to find a SOS.INTERP#090000. This is the
> same file which can be found on the included disk image, and contains the
> Apple ][ emulation module "Star Emulator" that I threw together about a
> year and a half ago.
>
> Emulation is spotty as hell.

On my XP box, it keeps running thru the test mode, warning that the disk
can't be accessed. Also, the disk image has a bad SOS.DRIVER. It is marked
as an empty, or deleted, file. Could this be the problem?

FYI, the disk image loads into AppleWIN just fine.

Bill

Steve Nickolas

On Mon, 26 Dec 2011, Bill Garber wrote:

> On my XP box, it keeps running thru the test mode, warning that the disk
> can't be accessed. Also, the disk image has a bad SOS.DRIVER. It is marked
> as an empty, or deleted, file. Could this be the problem?

It works on MESS...

I know the emulation is very poor, though.

> FYI, the disk image loads into AppleWIN just fine.

Yes, I know.

It's a dual mode 3/2 disk that has 48K EHBASIC+ 0.87 and 64K EHBASIC+ 0.87
in addition to Star Emulator. Star Emulator relies partly on SOS to "set
up" things - I don't know how to load a font yet, or how to create a fake
SOS.KERNEL, as opposed to a fake SOS.INTERP as currently.

-uso.