Oric DSK Manager
Re: Oric DSK Manager
Maybe there is an OS dependent problem here? Because I tried and the program failed for me when opening the disk image with the same symptoms. No matter if I use the Open menu or drag&drop. I am using Windows 10.
Re: Oric DSK Manager
Well, it seems something got messed up with the binary in version 0.4. I've checked that some errors arise when running the jar against a java 8 runtime environment, due to some changes in java 9. I was able to reproduce your problem by running it on a java 8 runtime.
Please find in this url a new version that should hopefully fix the problem at:
https://github.com/teiram/oric-dsk-mana ... er-0.5.jar
Please find in this url a new version that should hopefully fix the problem at:
https://github.com/teiram/oric-dsk-mana ... er-0.5.jar
Re: Oric DSK Manager
You rock!
Re: Oric DSK Manager
I don't have a problem with the Java language and I also did like Flash and Wordpress, what killed me is the insane number of security updates I had to do for all of these products, knowing that if you don't update you are at risk, and none of these updates are streamlined: You have to click and validate and checkboxes and click and restart and crap -> Too much work, trashcan.
Things that use java internally, using a locally installed runtime that does not try to talk to the internet, I don't care
It's working fine with version 0.5
I've a request there: Could you update your About dialog with the list of changes you are doing from version to version?
Windows 7, 64 bit version.
When I "Open DSK" the file selector defaults to "Computer" so I see the list of Hard Drives
Not criticaloverCLK wrote: ↑Wed May 09, 2018 8:09 am This was intentional. I didn't want to fight the layout manager and considered that there was enough room for all the information to display. It's true that when the disk has a lot of small files, you wouldn't be able to see all of them at once, and would need to scroll the disk view. Is this really a big drawback for you?
Feature request: Documentation page
Maybe you could add some quick save feature, to export in known formats:
-> Save as single sided 3"
-> Save as double sided 3"
-> Save as single sided 3.5"
-> Save as double sided 3.5"
With eventually warnings to indicate when something would not fit.
These days we have a bunch of people having a mix of different types of drives, it becomes very easy to to generate a program that does not run on some specific format.
Re: Oric DSK Manager
I had the intention to provide a self-contained executable, relying on the java 9 jigsaw feature (so that you don't need to deliver the whole JRE monster, only the parts you use and the user doesn't need to install anything). Unfortunately, it turned out to be quite difficult to make legacy libraries to run nicely under this approach. And probably I won't be able to be under 50Mb or so.
I agree that some sort of changelog should be available, but maybe in the github page itself. Take into account that this is in very alpha state and currently my aim is to make it work properly. Any feedback is appreciated though.
Is this happening to you on program restarts or during the same execution?
Fair enough. I will try to setup a wiki in the github project. The time I dedicate to this project is limited though, so maybe it's not going to happen today.
That would be a nice feature. Maybe we can provide some templates for the format (sides,tracks, sectors). The warning is currently available as the occupation bar should turn to red as soon as the needed disk space exceeds the chosen format.Dbug wrote: ↑Wed May 09, 2018 7:31 pm Maybe you could add some quick save feature, to export in known formats:
-> Save as single sided 3"
-> Save as double sided 3"
-> Save as single sided 3.5"
-> Save as double sided 3.5"
With eventually warnings to indicate when something would not fit.
These days we have a bunch of people having a mix of different types of drives, it becomes very easy to to generate a program that does not run on some specific format.
Re: Oric DSK Manager
On restart.
During the same execution it keeps the last selected location.
Re: Oric DSK Manager
I've a new bug report
ISS linked a patched Sedoric floppy on the viewtopic.php?f=25&p=17473#p17473 thread, I wanted to extract the patch files using ORIC DSK Manager, but when I tried to load it, I got an error dialog:
"Error in Archive Operation
See the application logs for further info"
The main difference is that this S30tpOK.dsk file is about 1 megabyte in size.
ISS linked a patched Sedoric floppy on the viewtopic.php?f=25&p=17473#p17473 thread, I wanted to extract the patch files using ORIC DSK Manager, but when I tried to load it, I got an error dialog:
"Error in Archive Operation
See the application logs for further info"
The main difference is that this S30tpOK.dsk file is about 1 megabyte in size.
Re: Oric DSK Manager
Also, PATCH.001 is a merged file (3 files in it).
Re: Oric DSK Manager
Good. I'm quite busy these days, but will take a look as soon as I get some spare time.Dbug wrote: ↑Fri May 18, 2018 9:02 am I've a new bug report
ISS linked a patched Sedoric floppy on the viewtopic.php?f=25&p=17473#p17473 thread, I wanted to extract the patch files using ORIC DSK Manager, but when I tried to load it, I got an error dialog:
"Error in Archive Operation
See the application logs for further info"
The main difference is that this S30tpOK.dsk file is about 1 megabyte in size.
Re: Oric DSK Manager
I think I've found the bug Dbug reported.
I was improperly decoding tracks when following the directory chain, normally it was not a problem as long as no directory entries were located in B-Side tracks.
Find attached a 0.6 snapshot version (just rename it from .zip to .jar) that should work with this disk and hopefully doesn't break anything.
I will defer the 0.6 version a bit to try to add also some of the requested features.
I was improperly decoding tracks when following the directory chain, normally it was not a problem as long as no directory entries were located in B-Side tracks.
Find attached a 0.6 snapshot version (just rename it from .zip to .jar) that should work with this disk and hopefully doesn't break anything.
I will defer the 0.6 version a bit to try to add also some of the requested features.
- Attachments
-
- oric-dsk-manager-0.6-SNAPSHOT.zip
- (236.39 KiB) Downloaded 439 times
Re: Oric DSK Manager
I think I could add a menu to set the format (sides,tracks,sectors) to one of these known formats. Can you please tell me what are the values for tracks and sectors for each of them?Dbug wrote: ↑Wed May 09, 2018 7:31 pm Maybe you could add some quick save feature, to export in known formats:
-> Save as single sided 3"
-> Save as double sided 3"
-> Save as single sided 3.5"
-> Save as double sided 3.5"
With eventually warnings to indicate when something would not fit.
These days we have a bunch of people having a mix of different types of drives, it becomes very easy to to generate a program that does not run on some specific format.
Re: Oric DSK Manager
Hello, overCLK! Great utility.
I've tested the github version with your last fix and there is no error message.
But when extracting the PATCH.001 file the result is 268 bytes which contain data only for the 1-st part (chunk) of 3 total. Here is the info which describes what PATCH.001 is and how to create it. The info is extracted from "SEDORIC 3.0 à NU". To create file is used: COPYM"P?"TO"PATCH.001" which merges the 3 parts. Unfortunately, I don't know more about Sedoric internals. Maybe @Symoon can help more (or anyone else)?
About the disk sizes, IMO standard sizes can be: 16/17/18 sectors on 40,41,42, 80,81,82 tracks. But maybe is would be better tracks to be free selectable.
I saw already your answer about resize-able main window and understand your point, but I really think it will be better to have at least vertical resize (just my 2cents) .
I've tested the github version with your last fix and there is no error message.
But when extracting the PATCH.001 file the result is 268 bytes which contain data only for the 1-st part (chunk) of 3 total. Here is the info which describes what PATCH.001 is and how to create it. The info is extracted from "SEDORIC 3.0 à NU". To create file is used: COPYM"P?"TO"PATCH.001" which merges the 3 parts. Unfortunately, I don't know more about Sedoric internals. Maybe @Symoon can help more (or anyone else)?
About the disk sizes, IMO standard sizes can be: 16/17/18 sectors on 40,41,42, 80,81,82 tracks. But maybe is would be better tracks to be free selectable.
I saw already your answer about resize-able main window and understand your point, but I really think it will be better to have at least vertical resize (just my 2cents) .
Re: Oric DSK Manager
Well, thanks. Glad that you like it.
My knowledge of French is even worse than my knowledge of Sedoric. But anyway:iss wrote: ↑Sat May 19, 2018 1:21 pm I've tested the github version with your last fix and there is no error message.
But when extracting the PATCH.001 file the result is 268 bytes which contain data only for the 1-st part (chunk) of 3 total.PATCH.001.png
Here is the info which describes what PATCH.001 is and how to create it. The info is extracted from "SEDORIC 3.0 à NU".
patch-001.pdf
To create file is used: COPYM"P?"TO"PATCH.001" which merges the 3 parts. Unfortunately, I don't know more about Sedoric internals. Maybe @Symoon can help more (or anyone else)?
I guess you would expect to have extracted a PATCH.001 with size 5 bytes. There are (were) two reasons why the extracted file is bigger:
- When a file has load/execution address or defined flags, the utility preserves this information in a 12byte header. The utility is also (hopefully) able to strip this header when the file is added to a DSK if it exists, and should take such metadata from this header.
- There was a bug, and the utility did not take into account the size of the file to export it, exporting instead whole 256 byte sectors, so the minimal file size would be 256 bytes.
This explains your 256 + 12 = 268 byte file.
I've corrected the bug and with the new version you would export a file of 5 + 12 = 17 bytes
The version in github master should also already support "remembering" the last used directory. I'm not attaching it here to avoid wasting more host space.
If you still want to export a 5 byte file, you can try setting to zero the load and exec address and unticking all the set flags of the PATCH.001 in the utility. Extracting it afterwards, you will have a file of 5 bytes, since the utility is able to decide whether it needs to export the header to preserve the metadata or not. In this way you would trick the program by making it think that no metadata is present and so no header is really needed.
When I designed it I thought it was a good idea. Maybe it is not after all.
I would like to have a set of standard formats to quickly set it from a menu, but I will keep the possibility to choose any combination of sides/tracks/sectors as it is now. So, what "named" formats could we offer? :
3" single/double side
3.5" single/double side
and what are the parameter for each of them?
Well, if you all think it's a good idea... I will add it to the TODO list in my head.
Re: Oric DSK Manager
Sadly I won't help much there. Even when I was working at understanding parts of Sedoric, I recall merged files were a pain and I never took time to understand at 100% since it sounded so exotic and not really used.iss wrote: ↑Sat May 19, 2018 1:21 pm Here is the info which describes what PATCH.001 is and how to create it. The info is extracted from "SEDORIC 3.0 à NU".
patch-001.pdf
To create file is used: COPYM"P?"TO"PATCH.001" which merges the 3 parts. Unfortunately, I don't know more about Sedoric internals. Maybe @Symoon can help more (or anyone else)?