PRINTAT64(0,0) not working on zxbasic-1.4.0s1995 (*solved*)

[Luzie]

Hi,

i try this on zxbasic-1.4.0s1995:

Code:

PAPER 7
INK 0
BORDER 7
CLS

BORDER 1

#include <print64.bas>

LOP:
PRINTAT64(0,0)
PRINT64("Test1234")
GOTO LOP

But this prints "Test1234Test1234Test1234" and so on and not just in the upper right corner?

[boriel]

could not reproduce.
I released ZX Basic 1.5.0 and the program behaved correctly.
Can you try with this version?

[Luzie]

.MSI and .EXE Downloads not working on Download-Page?

I unzipped ZIP-File and a zxb.exe --version shows: zxb 1.4.0-s1980

However File "version.py" contains "VERSION = '1.5.0'"

Tried my program with this ZXB.EXE but have same problems, maybe I should try a freshly installed ZXB.

[boriel]

.MSI and .EXE Downloads not working on Download-Page?

I unzipped ZIP-File and a zxb.exe --version shows: zxb 1.4.0-s1980

However File "version.py" contains "VERSION = '1.5.0'"

Tried my program with this ZXB.EXE but have same problems, maybe I should try a freshly installed ZXB.

Hi, luzie
My bad. The .exe version is on the way (I've updated the compiler toolchain, and have some problems with .exe file generation at the moment).
The 1.5.0 is because I overwrite the version file (nothing else).
For 1.4.0, try the version s1995 from the archive: <!-- m --><a class="postlink" href="http://www.boriel.com/files/zxb/archive/">http://www.boriel.com/files/zxb/archive/</a><!-- m -->
Don't use -O3 when testing.

[Luzie]

Hi,

I tried v1.5.1-Win32 and v1.5.0-Win32 but when I run ZXB.EXE I get this error:

Error loading Python DLL: c:\Program Files\zxbasic\python35.dll (error code 998)

...Update1 ...sorry, I think I must install Python 3.5... :oops:

...Update2: No, I installed Python v3.5.0 same error, than Python v3.5.2 also the same error above...

[boriel]

Yes, sorry. I'm aware of this problem. It seems to work on Windows 10, but not on Windows 7.
You don't need python to run .exe versions (that's the point of it!)
Which version of windows are you using? :roll:

[Luzie]

Yes, sorry. I'm aware of this problem. It seems to work on Windows 10, but not on Windows 7.
You don't need python to run .exe versions (that's the point of it!)
Which version of windows are you using? :roll:

I´ve tried on Windows 8.0. I will now try on Win10 and tell you here, how it´s working.

[boriel]

Yes, sorry. I'm aware of this problem. It seems to work on Windows 10, but not on Windows 7.
You don't need python to run .exe versions (that's the point of it!)
Which version of windows are you using? :roll:

I´ve tried on Windows 8.0. I will now try on Win10 and tell you here, how it´s working.

Thanks, Luzzie! I appreciate it.
I'm thinking in a workaround to this problem, nonetheless.

[Luzie]

Hi,

ZXB.EXE runs OK now that I use Win10 instead of Win8.

But the original Print64/PrintAt64-Problem still exists the same.

I tried to put the code and 3 screenshots together in a ZIP-File so you can test it, but I cannot attached this to a PM (File-Extension not allowed, even if I rename .ZIP to e.g. .TXT). Could you please send my your Email-Adress via PM, so I can directly send the .ZIP-File to you?

Regards,

Luzie

[boriel]

That's strange. I've tested your permissions and you can upload .ZIP files.
Even PM me.
I'll send you an email

[boriel]

Okay, can you download version 1.5.2? It should fix this problem.

[Luzie]

Okay, can you download version 1.5.2? It should fix this problem.

Hi, sorry for the delay. I tried with actual v1.6.2 and PRINTAT64 now works OK for me.

Regards,

Luzie

[Luzie]

Hi,

I tried again with v1.6.12 and v1.6.9 and the problem seems to be back?

[boriel]

Hmm. You mean a bug regression? Should not happen. Let me check...

[boriel]

According to this experiment, it's working as expected:

Code:

o#include <print64.bas>
DIM n,x,y as uInteger
CLS

FOR n=1 to 10000
    y=rnd*23
    x=rnd*63
    printat64(y, x)
    print64("ABCDEFGHIJKLMNOPQRSTUVWXYZ"(n MOD 26 TO n MOD 26))
    print at 23,0;n;"  y:";y;"  x:";x;"  L:";n mod 26; "    ";
NEXT n

pause 0
END

Which produces this .tap (see attached file).
Please, just in case, redownload 1.6.12, try again and tell me? :roll: