As a fan of WinImge for MS-DOS floppy disk images, I've wanted to see a similar GUI front-end for cpmtools for years. So I decided to createThe ability to make an image bootable by loading boot code into the boot
one. It's still in progress, and many of the features are still buggy,
so I'm not announcing it yet.
However, one feature WinImage has is the ability to make an image
bootable by loading boot code into the boot sector of the floppy image.
I'm wondering how feasible a similar feature would be with CP/M images
-- being able to save off the system tracks to, or overlay them from a
.bin file.
What considerations might there be?
I'm wondering how feasible a similar feature would be with CP/M images
-- being able to save off the system tracks to, or overlay them from a
.bin file.
What considerations might there be?
As a fan of WinImge for MS-DOS floppy disk images, I've wanted to see a similar GUI front-end for cpmtools for years. So I decided to create
one. It's still in progress, and many of the features are still buggy,
so I'm not announcing it yet.
However, one feature WinImage has is the ability to make an image
bootable by loading boot code into the boot sector of the floppy image.
I'm wondering how feasible a similar feature would be with CP/M images
-- being able to save off the system tracks to, or overlay them from a
.bin file.
What considerations might there be?
Please look there:
https://github.com/ProgrammingHobby/CPM_Image-File_Explorer/releases/tag/0.0.9.4
On 9/03/2024 8:59 pm, nathanael wrote:
As a fan of WinImge for MS-DOS floppy disk images, I've wanted to seeThe ability to make an image bootable by loading boot code into the boot sector of the floppy image would be a great feature, I look forward to
a similar GUI front-end for cpmtools for years. So I decided to create
one. It's still in progress, and many of the features are still buggy,
so I'm not announcing it yet.
However, one feature WinImage has is the ability to make an image
bootable by loading boot code into the boot sector of the floppy image.
I'm wondering how feasible a similar feature would be with CP/M images
-- being able to save off the system tracks to, or overlay them from a
.bin file.
What considerations might there be?
its development.
If you are looking for features to add, how about the ability to create
empty disk images?
CP/M resides in tracks 0 and 1 of a floppy disk. Does this mean the CP/M system will always start at offset 0 of a floppy image?
CP/M resides in tracks 0 and 1 of a floppy disk. Does this mean the CP/MYes. But .....
system will always start at offset 0 of a floppy image?
The problem with CP/M is that there are so many floppy disk formats out there. Theoretically you're right.
I've used this Windows version - http://star.gmobb.jp/koji/cgi/wiki.cgi?page=CpmtoolsGUI
- / & @ $ +
So it is not a Linux problem, it is a shell problem.
On 3/11/24 05:33, Nick wrote:
I've used this Windows version -
http://star.gmobb.jp/koji/cgi/wiki.cgi?page=CpmtoolsGUI
Interesting. I wasn't aware of this. Looks like I'll find some great
ideas there. Thanks.
--Nathanael - *HUMONGOUS* CP/M
On 3/11/24 11:03, yeti wrote:
So it is not a Linux problem, it is a shell problem.
True, but I do do a lot of work in BASH shells. But I also have to deal
with DOS, Windows and MacOS, so I need to find a solution compatible
with all of the above.
Also the translation should be reversible so the original CP/M filename
can be recovered. That restricts me to chars illegal under CP/M to avoid filename collisions and ambiguity.
I've looked through the SIG/M collection, and the only (potentially) problematic chars I've seen are - / & @ $ +
- @ and + are not, I think, problematic under other OSes, leaving / &
and $ to deal with.
/ has traditionally been translated to _. I'm considering mapping & to %
and $ to =. Depending on which source I believe % and = are illegal
under CP/M but not problematic under DOS, Windows or Linux, so I think that'll work.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 67:34:38 |
Calls: | 6,915 |
Files: | 12,379 |
Messages: | 5,431,813 |