@konc - its packed by my packer because it came from my collection 😀

@ripsaw8080 - The patch you removed is post compile, but was not added by me. not sure what its point was, the two decrements dont make much sense at all.

@leileilol - an original archive of it, nice!

leileilol wrote:

For puristnesses here's N.ARJ........renamed to a ZIP so this board can take it (it's still an ARJ)

Great! Thanks for this, I initially thought this was BloodyCactus' file in a format acceptable by this board as an attachment 🤣

A necro but with an update, maybe for the 0.12 people who might be interested in this

The original utility choked on large disk sizes, depending on the geometry even 100MB and certainly a bit more were enough to overflow something in calculations and mess the display like in collector's post. This was bothering me more than it should, so yeah you know how it goes in this hobby, here's a 1:1 clone from scratch that displays hundreds of MBs and even the GBs of FAT32. Top is the original, bottom my clone

konc wrote on 2026-01-09, 14:25:

A necro but with an update, maybe for the 0.12 people who might be interested in this […]
Show full quote

A necro but with an update, maybe for the 0.12 people who might be interested in this

The original utility choked on large disk sizes, depending on the geometry even 100MB and certainly a bit more were enough to overflow something in calculations and mess the display like in collector's post. This was bothering more than it should, so yeah you know how it goes in this hobby, here's a 1:1 clone from scratch that displays hundreds of MBs and even the GBs of FAT32. Top is the original, bottom my clone

The attachment N2.zip is no longer available

The attachment 01.png is no longer available

The attachment 02.png is no longer available

The attachment 03.png is no longer available

Hi,
Thanks, it works even with ~100 GB FAT32 partition but I do not fully understand the size calculation. It seems it uses neither 1024 nor 1000 as divider:
Full size and free space according to Windows (Windows uses 1024 as KB/MB/GB divider):

Full size and free space according to your program:

Falcosoft wrote on 2026-01-09, 14:56:

Hi, Thanks, it works even with ~100 GB FAT32 partition but I do not fully understand the size calculation. It seems it uses neit […]
Show full quote

Hi,
Thanks, it works even with ~100 GB FAT32 partition but I do not fully understand the size calculation. It seems it uses neither 1024 nor 1000 as divider:
Full size and free space according to Windows (Windows uses 1024 as KB/MB/GB divider):

The attachment p_win.png is no longer available

Full size and free space according to your program:

The attachment p_dos.jpg is no longer available

Hi and sorry for calling you 0.12 of a person 😀

You didn't understand the calculation because the fat32 part was obviously wrong, I updated the attachment and thanks for noticing this fast! It's supposed to be 1024, I think it looks fine now: 10098,32 / 1024 = 9.9GB rounded to 1 decimal. Nice though, it was never checked above the 32GB that pure DOS allows (with its own tools, I know a FAT32 partition can be larger) as the space allocated to maintain the original look doesn't allow more digits anyway. Curious to see if it matches your partition too now and again thanks for checking it out, this could have stayed wrong for ever.

konc wrote on 2026-01-09, 14:25:

A necro but with an update, maybe for the 0.12 people who might be interested in this[...]

I have also added this to my \UTILS directory, looking good as the last autoexec entry 😁

konc wrote on 2026-01-09, 16:14:

Hi and sorry for calling you 0.12 of a person :) […]
Show full quote

Falcosoft wrote on 2026-01-09, 14:56:

Hi, Thanks, it works even with ~100 GB FAT32 partition but I do not fully understand the size calculation. It seems it uses neit […]
Show full quote

Hi,
Thanks, it works even with ~100 GB FAT32 partition but I do not fully understand the size calculation. It seems it uses neither 1024 nor 1000 as divider:
Full size and free space according to Windows (Windows uses 1024 as KB/MB/GB divider):

The attachment p_win.png is no longer available

Full size and free space according to your program:

The attachment p_dos.jpg is no longer available

Hi and sorry for calling you 0.12 of a person 😀

You didn't understand the calculation because the fat32 part was obviously wrong, I updated the attachment and thanks for noticing this fast! It's supposed to be 1024, I think it looks fine now: 10098,32 / 1024 = 9.9GB rounded to 1 decimal. Nice though, it was never checked above the 32GB that pure DOS allows (with its own tools, I know a FAT32 partition can be larger) as the space allocated to maintain the original look doesn't allow more digits anyway. Curious to see it matches your partition too now and again thanks for checking it out, this could have stayed wrong for ever.

The attachment SCREEN01.png is no longer available

Yep, it is working perfectly now!

Very Nice! Years ago I originally patched it to cap out at 512mb disks to stop it breaking and printing garbage, and never really worried about it.

your solution is nicer 😀 (I did strip the debugging info off and re-pack it).

keropi wrote on 2026-01-09, 16:34:

I have also added this to my \UTILS directory, looking good as the last autoexec entry 😁

Yay welcome to the club, I'm an influencer now!

Falcosoft wrote on 2026-01-09, 17:27:

Yep, it is working perfectly now!

Great! Thanks for testing.

BloodyCactus wrote on 2026-01-09, 18:34:

Years ago I originally patched it to cap out at 512mb disks to stop it breaking and printing garbage, and never really worried about it.

So I wasn't the only one annoyed so much by this completely unimportant thing, it's good to know. My first thought was also to try and fix it somehow, to avoid basically the donkey work of recreating the 3x3 font, but it uses INT 21h so it would max out at 2GB anyway.