snip<=-
snip<=-
This was followed by a full screen of info, but...
How can my magic number be wrong? Why do I have a magic number? :)
Has anyone else seen this? I can run it fine on the Windows system,
but I'd prefer to run it on this Linux system...
On 12-05-18 15:00, apam wrote to Black Panther <=-
I know I'd prefer to use it on Linux too, but you'll get much less frustration on windows.
So, I've been trying to do a little ANSI work, and for some reason PabloDraw is giving me problems. It will let me open the file, but when
I go to edit it, the program crashes and I get the following:
xqtr wrote to Black Panther <=-
So, I've been trying to do a little ANSI work, and for some reason PabloDraw is giving me problems. It will let me open the file, but when
I go to edit it, the program crashes and I get the following:
Same thing here... on a fresh install of lubuntu 18.10 with lxqt. But
in my previous system with lubuntu 16.04 was working fine. :(
Somethings I could do and make it crash, like click and drag backwards, other times it just randomly crashed. Maybe it depends on a particular version of mono as I think Pablodraw hasn't been updated in a while.
I know I'd prefer to use it on Linux too, but you'll get much less frustration on windows.
So, I've been trying to do a little ANSI work, and for some reason PabloDraw is giving me problems. It will let me open the file, but wh I go to edit it, the program crashes and I get the following:It seemed to work alright here under Ubuntu 18.04. It was after
Same thing here... on a fresh install of lubuntu 18.10 with lxqt. But in my previous system with lubuntu 16.04 was working fine. :(
upgrading to 18.10 that I started having some issues with a few programs
I was using... :(
I didn't notice what version of PabloDraw i was using in my old system,
so i can't tell if the problem is in Ubuntu or Pablo. If PB hasn't been updated for a while.. then its Ubuntu's problem.
Nevertheless, in 2018, we shouldn't depend on a Windows/Mono program to view/edit ANSI files :( I haven't used Wine for a long time and i was forced to, to use some ANSI viewers/editors.
I have started making a simple ANSI viewer for my self, in Linux with Lazarus/Freepascal. If and when i have it on a certain level, i will release it for others too.
On 12/06/18, xqtr said the following...
I didn't notice what version of PabloDraw i was using in my old s
so i can't tell if the problem is in Ubuntu or Pablo. If PB hasn' updated for a while.. then its Ubuntu's problem.
I'm thinking it's an issue with Ubuntu, as PabloDraw hasn't been
updated since 2013...
My version will only work on windows and Linux (No macos support). It
seems to run fine with OpenSUSE with mono 5.10.
I'll upload it to your BBS, It's just an exe file in a zip file, if you can verify it works with Ubuntu, (Ubuntu has an outdated mono), that
would be good.
snip<=-
snip<=-
On 12/07/18, apam said the following...
I'll upload it to your BBS, It's just an exe file in a zip file,
can verify it works with Ubuntu, (Ubuntu has an outdated mono), t would be good.
Thank you. I gave it a try on the Ubuntu 18.10 system, and got this:
Thank you. I gave it a try on the Ubuntu 18.10 system, and got this:
try sudo apt-get install gtk-sharp3
That seemed to do it. It working almost 100% now. There are still a few ANSI screens, when I try to view them, PB will throw an error message that starts with the 'magic number' being wrong. At least it doesn't crash the program like it did before.
Hmm, would it be possible to send me those ansis? I can have a look and see if I can fix it.
No promises though, it's a pretty complex program lol
I just uploaded them to The Fat Sandwich. What I just noticed though, is if I get the error message, then try another file, then go back to the one that gave the error, it will load. (I hope that made sense...) :)
You've already done more than expected... Much appreciated... :)
That seemed to do it. It working almost 100% now. There are still a
few ANSI screens, when I try to view them, PB will throw an error
message that starts with the 'magic number' being wrong. At least it doesn't crash the program like it did before.
A quick google.. apparently that's a mono bug. To get around it type:
export TERM=xterm
mono PabloDraw.exe
Hope that helps.
A quick google.. apparently that's a mono bug. To get around it type: export TERM=xtermThat did help. I added that to the startup script I wrote for PB, and
mono PabloDraw.exe
just went through the entire mystic/text directory, and was able to view every ANSI file.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 216:13:09 |
Calls: | 14,143 |
Calls today: | 1 |
Files: | 295 |
Messages: | 551,126 |