Using TAPETODISK with a nanoPEB

[sparkdrummer]

I'm working on a project with one of my nanoPEB's.

I am attempting to use a wonderful program called TAPETODISK.

What it does is take a cassette tape that is full of programs and transfer them one at a time to DSK1. You set it and forget it until it finishes.

It works great on real iron.

The problem is when using with a nanoPEB it will read the tape ok but when it goes to save to disk the screen just locks. No save to disk.

I'm wondering if any of our programming giants might take a look at it and see what gives?

And maybe fix it for nanoPEB use?

If so, it would be great if a drive selection of 1 to 3 could be implemented as well.

TAPETODISK

[Tursi]

Nothing gets called out by the Classic99 DSR, but the NanoPeb DSR gets stuck in a loop. I'm not sure what it's trying to do - the code it's in doesn't line up with the TI controller DSR and we don't have source for it.

 

[sparkdrummer]

Bummer.

Thanks for looking Tursi!

[+Lee Stewart]

1 hour ago, sparkdrummer said:

The problem is when using with a nanoPEB it will read the tape ok but when it goes to save to disk the screen just locks. No save to disk.

 

Seeing this line:

191 CALL LOAD(-31888,63,255)

which stores >3FFF in >8370 (highest available VRAM address), tells me the program explicitly manipulates the presumed TI/CorComp/?? Disk Controller DSR’s disk buffer area of high VRAM, which presumption is off by 8 bytes for the nanoPEB DSR. I think you would need to rewrite the ALC that gets loaded with this program to be either a bit more generic or specific to the nanoPEB. It might be possible to get it to work by changing the references to >3FFF (line 191) and >3FE8 (line 210), but the loaded machine code would also need to be patched, which, of course, is not so easy.

 

...lee

[sparkdrummer]

Thanks for looking Lee. I was hoping for the best, but it looks like nanoPEB’s funky code strikes again. 

[Tursi]

14 hours ago, sparkdrummer said:

Thanks for looking Lee. I was hoping for the best, but it looks like nanoPEB’s funky code strikes again. 

That explains a lot...

 

The NanoPEB is funky, yeah, but this is the same crap that has been an issue since the early days - all software assumes it's talking to a TI Disk Controller and instead of using the TI-provided interface, they reach in and directly manipulate things. Then, surprise, it fails on different hardware.

 

[+arcadeshopper]

8 hours ago, Tursi said:

That explains a lot...

 

The NanoPEB is funky, yeah, but this is the same crap that has been an issue since the early days - all software assumes it's talking to a TI Disk Controller and instead of using the TI-provided interface, they reach in and directly manipulate things. Then, surprise, it fails on different hardware.

 

[sparkdrummer]

That’s the guy from UHF - “You so stoopid!” 

[Tursi]

"NOTHING! ABSOLUTELY NOTHING!"