You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure wether this is driver or GEOS related, but with the german language version of GEOS 2.0 and 2.5 I can reproduce the following issue:
start GeoWrite and load a text document or create a new one and just type some words.
print the document to a CUPS printer using ras4c64net
the print will complete successfully on the CUPS printer
once the print is complete, exit GeoWrite to Desk Top (it's the vanilla Desk Top I'm using here, not Top Desk or any other replacement)
Once Desk Top has finished loading, a popup will show "Error near $025D" and GEOS freezes. This happens with german GEOS 2.0 and german GEOS 2.5
If I repeat the above steps on an english language GEOS 2.0 there is no such problem and the system continues to operate without any problem.
If you are interested, I can attach my the GEOS 2.5 (German) D81 Image or the original G64 images I am using.
EDIT:
I can open / create and edit a document, exit GeoWrite and return to Desk Top without the error if I do not print the document.
The text was updated successfully, but these errors were encountered:
lodger-c64
changed the title
Error near $025D on german language Versoin od GEOS 2.0 and 2.5
Error near $025D on german language Version of GEOS 2.0 and 2.5
Oct 16, 2022
I am not sure wether this is driver or GEOS related, but with the german language version of GEOS 2.0 and 2.5 I can reproduce the following issue:
If I repeat the above steps on an english language GEOS 2.0 there is no such problem and the system continues to operate without any problem.
If you are interested, I can attach my the GEOS 2.5 (German) D81 Image or the original G64 images I am using.
EDIT:
I can open / create and edit a document, exit GeoWrite and return to Desk Top without the error if I do not print the document.
The text was updated successfully, but these errors were encountered: