Denial

Mike wrote: ↑Fri Mar 07, 2025 12:18 pm Small teaser:



... works as supposed.

I like this very much. Neat with a cable adapter that just makes it work without internal modifications!

It looks and plays fantastic! Congratulations!

Normal files with USR type, as an 'alternative' to SEQ type files, or actual drive utility files (loaded by CBM DOS directly into drive RAM and executed there) should not pose any problems. You are concerned about GEOS VLIR files? Yes, the GEOS file type is a specific example of the problem. Since ...

So what does File Conductor do? Like Mike said, file management stuff. The advantages are: • Simple controls that should be somewhat intuitive to a modern computer user • Fully recursive directory operations copy, move or delete. • Proper error handling. Lots of work went into giving useful alterna...

Mike wrote: ↑Fri Sep 13, 2024 10:27 am May I suggest you use MG BROWSE to view the instructions?

Ah, yes. I didn’t spend any time on the instructions really since it’s at an experimental stage. Good point.

I have made an experimental port of File Conductor for the C128 to VIC20. You can try it out and tell me what works and what doesn't, what you like and don't like. It's made to handle lots of files and won't be useful with a single floppy drive. It starts to be useful with several drives and mass st...

What do you mean by screen editor? Do you want to edit the entire screen? Does that include scrolling? Only one line? Do you need special keys with different meaning than in the BASIC editor? What are you going to do with it?

doug_in_nc wrote: ↑Wed Jul 24, 2024 5:32 amI was going to check last night, but when I kicked up my VIC, it had died so I am going to either get it working or get another one out of storage. Hopefully I can give you the info you need by the end of the weekend.

Thanks for trying to assist!

Does Protecto ensure location 214 in memory reflects the current screen line? If you place the cursor on the first line, what does PRINTPEEK(214) print? And if on the last line?

I'm not near home right now to check, but off the top of my head, BASIC reports a bit over 31,000 bytes free on boot-up with a 16K, 8K and 3K RAM expansion added, so pretty close to the 32K you are using on the C128. Ah, yes. With 24 kB expansion I have a piece of the unexpanded 5 kB to chew on as ...

The file manager has matured a bit now and consumes almost 32 kB on the C128. So that will rule out any use of 40- or 80 column solutions unless they use external screen memory. Cutting some features may bring it down closer to 24 kB and use the top bank for variable storage.

The screenshot looks nice! This would be a very challenging project though. It kind of requires double buffering and it’s not the VIC’s strength because of the limited graphics memory.

This looks fantastic! The wall perspective suits the hardware and hides the wide pixels nicely. Good choice to use hires.

Merytsetesh wrote: ↑Thu Mar 14, 2024 12:21 pm If I had one mod for the VIC KERNAL, it would be to amend the screen routines to take account of variable dimensions instead of relying on the hardcoded values...

Yeah, asking for the screen size returns hard coded values. It would have been nice if that was dynamic, but sadly too late.

I tried a couple of file browsers before I started making my own. I didn’t like the ones I tested because they didn’t feel intuitive to me. Lots of keys to remember or small inconveniences like for example CBM Command overwriting files without asking and using @: which triggers the dreadful 1541 bug...