I'll get that fixed over the next couple of days.
EDIT: I managed to get it sorted in a short space of time, so I've uploaded version 1.38.3.
I'll get that fixed over the next couple of days.
Next release will be fine.geraldholdsworth wrote: ↑Mon Jan 03, 2022 3:04 pm I've enabled the "Change Interleave" method for any ADFS image, where the interleave method is forced. This will be on the next version - if you need it now, I can build and upload it. For now I've converted the above image to sequential, which works in BeebEm.
Yes, I think it probably has been addressed, but I've not had a chance to test yet. Although I'm still not sure what the Access Violation error is about when I try to create a new ADFS HDD image using the GUI?geraldholdsworth wrote: ↑Sun Jan 16, 2022 12:52 pm Hiya,
I'll reply to this over on the other thread, keep it all together, but as this was posted mid-way through the other thread, I'm suspecting you may have solved the issue?
Cheers,
Gerald.
Interesting...I'll look into this.
I can't replicate this, neither in the GUI or command line.
I'm running this on a Win10 x64 machine. I've copied the executable into a subfolder of the desktop, and I'm running it from there. I'm just using the defaults for a ADFS HDD:geraldholdsworth wrote: ↑Sun Jan 16, 2022 7:07 pmI can't replicate this, neither in the GUI or command line.
What options are you using when you create an image?
Thanks for investigating and I hope you find a solution!geraldholdsworth wrote: ↑Thu Jan 27, 2022 1:44 pm Looks like this bug is nothing to do with the production of a UEF - the entire data array is one byte too long, and could also manifest itself with other formats. Not sure why this would be, mind.
It was a 100K 'ssd' DFS disc from https://www.stairwaytohell.com/essentia ... rtDisc.zip. The zip file contains the disc image and a small text file. It was just that they were the two files to hand.geraldholdsworth wrote: ↑Sun Jan 30, 2022 11:14 am What image format did you try this with (i.e. DFS, ADFS) and which sub-format, if applicable (i.e. for ADFS: S,M,L,D,E,E+,F,F+)?
It's working well on Big Sur on M1, and the weird Open dialog bug seems to have gone away too!geraldholdsworth wrote: ↑Sat Feb 26, 2022 11:17 am I am pleased to finally announce version 1.39 is now available, including the code from UEF Reader. This is the first version compiled with the new version of Lazarus, so hopefully should fix the Windows scaling issues. I also have compiled for the Apple M1 chip, but I can't test this out myself.
Thank you so much for this. It's something that's bugged me for at least the last 6 versions of macOSXgeraldholdsworth wrote: ↑Fri Mar 11, 2022 12:14 pm I've often wondered how one would persuade macOS to add an application to the 'Recommend Apps' when opening a file, or to the 'Open With' menu. And then I found out. All one has to do is add the extensions the application can deal with into the info.plist file inside the .app.
billcarr2005 wrote: ↑Fri Mar 11, 2022 12:54 pm i then used Gerald Holdworth's Disk Image Manager to extract the rest of the graphics and text files, before adding them to the DSD, again via the excellent Disk Image Manager.
However, I noticed that it only allows 31 files to be copied (unless I missed a setting somewhere) so I copied the remainder onto another SSD which then got copied over to the DSD
No, I've missed that one - thank you.
As the OP, i thought I'd best clarify.geraldholdsworth wrote: ↑Sat Mar 12, 2022 9:27 am
No, I've missed that one - thank you.
It's an interesting issue to get around - not a bug, per se, but more of a DFS limitation. I'll need to ponder this to figure out a way to split the files across the two sides of a DSD (i.e., how to decide which goes where).
Cheers Bill.billcarr2005 wrote: ↑Sat Mar 12, 2022 9:58 am As the OP, i thought I'd best clarify.
The DSD was formatted as 80 track, Watford DFS 62 files, so it was actually the fact it only allowed 31 files on one side that was the issue... when I dragged over 41 files which had been extracted from the ADL - so they were the data & INF files, it stopped when the total number hit 31