Create multiple files on the GEOS disk #2
Comments
|
Ah yes, I remember that problem now.
I think the problem is in the units it uses for managing the disk image. I think I have fixed the bug in the D64Explorer tool which is based on the same units.
I see you're compiling yourself so you could try taking those units from D64Explorer and put them in GEOSBuild and see if the bug is fixed. If not, I can look at doing this tomorrow.
Daniel.
…________________________________
From: Xander Mol ***@***.***>
Sent: 14 January 2023 01:07
To: M3wP/GEOSBuild ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [M3wP/GEOSBuild] Create multiple files on the GEOS disk (Issue #2)
Sorry to bother you again. I have been succesful in building GEOS disks with a single application generated by CC65 on the disks. Works perfect,
However, I want to create a set of tools that ideally would be on the same disk.
As you have yourselves already indicated in your Solitaire game (https://github.com/M3wP/M3wPSolitaire , nice game by the way):
'There is presently a bug in the GEOSBuild tool which will occasionally causes problems so the disk image needs to be deleted before calling it.'
So opening an already created disk to write another app to it does not work from calling the existing image with a new GEOSBuild job. I indeed get issues, not even occasionally, but always. It gives the message 'Exception at 00000000004884D7: ED64InvalidSector:
Track #2<#2> does not contain 40 sectors.' if I try to add a second program.
Neither do I see in the documentation a way to add more than one file in one go.
Do I miss something? Any progress on this bug?
Environment used:
I have compiled your latest GEOSBuild repo with the latest Lazarus IDE Debian image for Uvuntu 20.04.5 LTS running under Windows 11/WSL2.
—
Reply to this email directly, view it on GitHub<#2>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACNUI57PU2OF377HQNNTRC3WSFVSPANCNFSM6AAAAAAT2QIIU4>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Yes, super! Dropping C64D64Image.pas and C64D64ImageStrs.pas from D64Explorer in GEOSBuild and compile again indeed works! I have now succesfully created a multifile disk with GEOS file. Only thing that is different is that the resulting image no longer is recognised directly by GEOS as a GEOS disk, while with the old GEOSBuild compile it was directly recognised as being GEOS. So thanks! |
|
Interesting... I'll have to look at the GEOS disk setting in D64Explorer then since it will have the bug, also.
Thanks for using the tools!
…________________________________
From: Xander Mol ***@***.***>
Sent: 14 January 2023 08:06
To: M3wP/GEOSBuild ***@***.***>
Cc: M3wP ***@***.***>; Comment ***@***.***>
Subject: Re: [M3wP/GEOSBuild] Create multiple files on the GEOS disk (Issue #2)
Yes, super! Dropping C64D64Image.pas and C64D64ImageStrs.pas from D64Explorer in GEOSBuild and compile again indeed works!
I have now succesfully created a multifile disk with GEOS file.
Only thing that is different is that the resulting image no longer is recognised directly by GEOS as a GEOS disk, while with the old GEOSBuild compile it was directly recognised as being GEOS.
But that is quickly solved by pressing OK on the 'Convert to GEOS' prompt in GEOS.
So thanks!
—
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACNUI574OFKYGB4S5ZZGQETWSHGU7ANCNFSM6AAAAAAT2QIIU4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Just released the first alpha release of my first project using a.o. your GEOSBuild tool: |
|
How awesome!
🙂
Sorry I couldn't get to fixing the image conversion in the editor tool. I have ended up being rather busy and haven't been able to access my archives as yet. Quite frustrating!
…________________________________
From: Xander Mol ***@***.***>
Sent: 29 January 2023 09:58
To: M3wP/GEOSBuild ***@***.***>
Cc: M3wP ***@***.***>; Comment ***@***.***>
Subject: Re: [M3wP/GEOSBuild] Create multiple files on the GEOS disk (Issue #2)
Just released the first alpha release of my first project using a.o. your GEOSBuild tool:
https://github.com/xahmol/GeoUTools
—
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACNUI533VIHIOX6SR2WJZN3WUWXB5ANCNFSM6AAAAAAT2QIIU4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
No problem. We all do this as unpaid hobbies so I perfectly understand other stuff happens 😉 |
|
Well.. I do remember diagnosing the problems so its likely I have worked on it already but...
In GEOSGraphics.pas you'll need to check the routines:
procedure GEOSDecompactBitmap(const ADataIn, ADataOut: TStream);
procedure GEOSCompactBitmap(const ADataIn, ADataOut: TStream);
You'll need the relevant sections of the GEOS Programmer's Reference Guide to confirm the behaviour of the routines. If you compare the two, you might see a difference but the routine is relatively complex.
If you check the compiled-in binaries with GEOSDesigner, you might get there... Its not hard to read the binary when you get used to the patterns used in the compression.
If you can confirm that instead those routines are functioning correctly, the problem may be in the user interface... You could check that first (where those routines are used in the DataModule or Forms) if you wanted something easy to check off, first.
Daniel.
…________________________________
From: Xander Mol ***@***.***>
Sent: 29 January 2023 21:09
To: M3wP/GEOSBuild ***@***.***>
Cc: M3wP ***@***.***>; Comment ***@***.***>
Subject: Re: [M3wP/GEOSBuild] Create multiple files on the GEOS disk (Issue #2)
No problem. We all do this as unpaid hobbies so I perfectly understand other stuff happens 😉
But could proceed with finding an alternative tool to edit icons (not being file icons) under Windows.
If I can help you on testing a fix on your tool, let me know.
—
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACNUI5YKEIMK5NJEQARLAKLWUZFXNANCNFSM6AAAAAAT2QIIU4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry to bother you again. I have been succesful in building GEOS disks with a single application generated by CC65 on the disks. Works perfect,
However, I want to create a set of tools that ideally would be on the same disk.
As you have yourselves already indicated in your Solitaire game (https://github.com/M3wP/M3wPSolitaire , nice game by the way):
'There is presently a bug in the GEOSBuild tool which will occasionally causes problems so the disk image needs to be deleted before calling it.'
So opening an already created disk to write another app to it does not work from calling the existing image with a new GEOSBuild job. I indeed get issues, not even occasionally, but always. It gives the message 'Exception at 00000000004884D7: ED64InvalidSector: Track #2 does not contain 40 sectors.' if I try to add a second program.
Neither do I see in the documentation a way to add more than one file in one go.
Do I miss something? Any progress on this bug?
Any suggestion if building with more than one file per disk is not yet possible on how by CLI commands combine the created disks into one combined disk?
I can perfectly do it with DirMaster, but as that is no CLI program I can not use that in an automated build pipeline.
I have tried using the VICE c1541 tool (again), but alas also -geosread or -geosextract do not seem to work on the disks created by GEOSBuild.
Environment used:
I have compiled your latest GEOSBuild repo with the latest Lazarus IDE Debian image for Uvuntu 20.04.5 LTS running under Windows 11/WSL2.
The text was updated successfully, but these errors were encountered: