Disk Jockey v4 for macOS is out

[OneGeekArmy]

A better interface, a brand new Inspector for your files, support for more formats (NDIF, UCSD Pascal, Atari ST hard drives and more).

See your files' data as hex, preview their contents when possible (for example: read your AppleSoft Basic listings directly or check out Atari ST images in Degas format).

It still runs on Mac OS 10.13 and up (many bug fixes for the older versions) and it's still free.

The release notes are here: https://diskjockey.onegeekarmy.eu/files/diskjockey/Disk-Jockey.app.html

Phew. I need a nap.

Disk Jockey

Disk Jockey, a disk image file maker for your retro stuff

diskjockey.onegeekarmy.eu

@JDW : This version parses the Apple II images you provided me with a few months ago. Some of them were in the UCSD Pascal format and it's now supported.

 

[JustG]

It still runs on Mac OS 10.13 and up (many bug fixes for the older versions) and it's still free.

Thank you for continuing to build this for older OS versions! I like to compartmentalize my interests between modern computers and the one I mainly use to support my old computers runs 10.14.

 

[OneGeekArmy]

Thank you for continuing to build this for older OS versions! I like to compartmentalize my interests between modern computers and the one I mainly use to support my old computers runs 10.14.

My goal is to try and support older Macs as long as possible (which I think makes sense for an application aimed at retro enthusiasts).

I'm not sure how long the inevitable march of progress (and, let's face it, Apple) will let me do this before my development toolchain no longer lets me do it. But as long as it does, 10.13 will remain the target.

(Especially since I finally have a working 10.13 machine for testing )

 

[JDW]

Fantastic work, @OneGeekArmy !

Love the icon too!

 

[OneGeekArmy]

Fantastic work, @OneGeekArmy !

Love the icon too!

View attachment 22769

Thank you. It's the work of maxtron95 (https://github.com/maxtron95) who sent it to me out of the blue one day (including the SVG file and everything - I was amazed). Since it's an order of magnitude better than my poor attempt, I had to make use of it.

 

[eric]

@OneGeekArmy made some tips and tricks videos as well

 

[JDW]

Snow? This is the first I've heard of it. Something new?

 

[OneGeekArmy]

Snow? This is the first I've heard of it. Something new?

You're in for a treat: https://snowemu.com/

 

[eric]

Created a thread for it https://tinkerdifferent.com/threads/snow-emu-emulator-for-680x0-based-macintosh-computers.4561/

 

[Elosha]

I really like the new version, and as already said elsewhere, thanks for keeping up support for "old" host OSes. (Keeping High Sierra around for 32bit Support and EFI experiments.)

However, it still believes all of my FAT12-Floppies (MS-DOS, NT, firmwares like ARC, EISA etc.) were Atari ST. And while the infotext claims they would be not exactly the same as MS-DOS-formatted disks, it can´t differentiate the formats. As many retro people also like MS-DOS, I personally expected it should be able to either differentiate or be more generic when it comes to FAT12. Are there any plans?

 

[OneGeekArmy]

I really like the new version, and as already said elsewhere, thanks for keeping up support for "old" host OSes. (Keeping High Sierra around for 32bit Support and EFI experiments.)

However, it still believes all of my FAT12-Floppies (MS-DOS, NT, firmwares like ARC, EISA etc.) were Atari ST. And while the infotext claims they would be not exactly the same as MS-DOS-formatted disks, it can´t differentiate the formats. As many retro people also like MS-DOS, I personally expected it should be able to either differentiate or be more generic when it comes to FAT12. Are there any plans?

View attachment 22816

OMG what an oversight on my part Apologies for that.

Would you mind zipping up floppy images from a couple of different platforms that support FAT12 and sending them my way? Non-DOS preferably so I can spot the eventual differences.

I'll see what I can do

 

[Elosha]

@OneGeekArmy I will, but probably easiest would be to
a) Rather detect the ATARI OEM signature "Loader". Because PCs would use OEM signatures "MSDOS", "PCDOS", "SYSLINUX", "VGACP", "MSWIN4" or others + version numbers … plus accidents like "G8q3IHC" ("xxxxxIHC") that result in mangling by 32bit Windows. Even my Alpha FW Update and EISA ECU Diskettes use "MSDOS" for compability.
As this is complicated …
b) Just switch by extension, use ATARI if the ending is ".st", as the others could be ".img" or ".imd" or ".vcp" or ".dd"

Anyway thanks for listening to these ideas

 

[OneGeekArmy]

@OneGeekArmy I will, but probably easiest would be to
a) Rather detect the ATARI OEM signature "Loader". Because PCs would use OEM signatures "MSDOS", "PCDOS", "SYSLINUX", "VGACP", "MSWIN4" or others + version numbers … plus accidents like "G8q3IHC" ("xxxxxIHC") that result in mangling by 32bit Windows. Even my Alpha FW Update and EISA ECU Diskettes use "MSDOS" for compability.
As this is complicated …
b) Just switch by extension, use ATARI if the ending is ".st", as the others could be ".img" or ".imd" or ".vcp" or ".dd"

Anyway thanks for listening to these ideas

The (completely self-imposed) constraint regarding file extensions is that I don't want to use them as an indicator of the file type. They are unreliable (people can change them at will) and, once you start supporting formats coming from different systems, they name clash (an ".img" is different on a PC or on a Mac and, on the ST and others, it's a picture format ).

As for signatures, "Loader" only appears on bootable ST floppies so that's not sufficient. It's a bit of a pickle.

But I'll figure out something eventually