Yes, the first load of VB81 can hang with this error!
It seem to be a "loop" error to prepare the Vb workspace system.
I had to reload it.
May be the anti-virus protection who add a launch latences on OCX, DLLs…
On W10, this bug was trapped with a system update.
Windows add a launch screen how avoid this error!
I worked on a new release, enclose the Centronics emulation and some corrections.
VB81 XuR: "07-09-19"
[edit: update available]
Place new ROMs in the ROMs directory.
Memotech SIF and CIF not connected.
Centronics seen working.
"Save binary" using a REM line: ok.
The timer overclocking is back, but can hang the keyboard typing (use it to print/calculate…) and you had to reset it to enter something on the keyboard.
Some other bugs fixed too…
Another (hidden) bug fixed.
[Note: This function can't be use on an unexpended D_File screen! The ZX81 will hang or reboot… i tried it!]
The new BIN/SCR D_File loader can now load old, and new saved files!
Working on the Memotech SIF card…
All the best.
Another update to load the Memotech Memotext ROM... if it's available.
The Memotech CIF isn't link yet, the BIOS jump wasn't dumped.(this tread)
...or...Test the Memotech Centronics card alone and dump only 3 PEEKs:
10 PRINT PEEK(2169)
20 PRINT PEEK(2170)
20 PRINT PEEK(2171)
For example, 20;01 is listed as JR +2 instead of JR +1, this can be confusing if you don't remember that. On the other hand backward jumps are listed correctly.
Bitwise manipulations involving IY or IX are all messed up, see the attached.
Lest I give you the wrong idea, I find "VB81 XuR" great and use it exclusively for any projects I'm working on, maybe that's why I've noticed these bugs. Even the lack of WRX support isn't that much of a problem. I just test programs using Quicksilva's hires mode first, then convert it to run using WRX later on, when debugged.
Vb81 r 03-10-2019
A new release to add Jpg, gif, pgn pictures formats.
The "multicolumn" zxPrinter is now able to save the listing in a PDF file.
(Memotech Cif not working (no rom dump); Memtext not available)
(don't forget to add the "libhpdf.dll" in the executable directory !)
10 LET X=16623
Produces a false error message!
10 LET X=Val "16623"
Avoids the error message.
I've seen this bug before with other values as well, weird huh.
See the attached.