QDT is (very) nice, but will most probably not run in the Black Box due to lack of at least 2 Million colors
Tobias
Pointer Environments
-
- RWAP Master
- Posts: 2839
- Joined: Sun Nov 28, 2010 4:51 pm
- Location: Stone, United Kingdom
- Contact:
Re: Pointer Environments
Great to hear that Jim has now made QDT freeware
Rich Mellor
RWAP Software
RWAP Adventures
SellMyRetro
Retro-Printer Module - add a USB printer to your QL
Also Involved in:
Icephorm
RWAP Software
RWAP Adventures
SellMyRetro
Retro-Printer Module - add a USB printer to your QL
Also Involved in:
Icephorm
Re: Pointer Environments
I got the same problem on my Trump Card to now trying to test QTRANS on my Winnybelg4rion67 wrote:Hi guys, I try to use PE on my QL with trump card 2 and qimi interfaces and things seems to go fine but I've some troubles with qtrans program: it starts but after it design screen with menus and buttons it displays this error:
qtrans_error.jpg
My system has two floppy drives and before launch qtrans I have configured it to use in right panel flp1_ and in left panel flp2_ but in another snap you can see that it not accept my configs
qtrans.jpg
Can somebody give me a tip to resolve?
Thanks
Paolo
Re: Pointer Environments
It seems to be an issue with the FNAME$ function in Toolkit 2 which works differently in some systems when used on a directory channel to return the name of the directory connected to that channel number. IIRC, on level 2 systems it returns a directory name, on level 1 filing systems it should (and does on ones I tested in 2013) return "" but on some systems which were level 1 and added a device with level 2 it gives 'bad parameter' instead, maybe the device concerned doesn't support this variant of FNAME$, I'm really not sure. I remember looking at this back in 2013 and was unable to resolve the issue reliably.Outsoft wrote:I got the same problem on my Trump Card to now trying to test QTRANS on my Winnybelg4rion67 wrote:Hi guys, I try to use PE on my QL with trump card 2 and qimi interfaces and things seems to go fine but I've some troubles with qtrans program: it starts but after it design screen with menus and buttons it displays this error:
qtrans_error.jpg
My system has two floppy drives and before launch qtrans I have configured it to use in right panel flp1_ and in left panel flp2_ but in another snap you can see that it not accept my configs
qtrans.jpg
Can somebody give me a tip to resolve?
Thanks
Paolo
When I get time I'll look at it again to see if there's a different way I could write the code to work around it, as with anything at the the moment TIME is the big problem.
--
All things QL - https://dilwyn.qlforum.co.uk/index.html
All things QL - https://dilwyn.qlforum.co.uk/index.html
Re: Pointer Environments
Thanks Dilwyndilwyn wrote:It seems to be an issue with the FNAME$ function in Toolkit 2 which works differently in some systems when used on a directory channel to return the name of the directory connected to that channel number. IIRC, on level 2 systems it returns a directory name, on level 1 filing systems it should (and does on ones I tested in 2013) return "" but on some systems which were level 1 and added a device with level 2 it gives 'bad parameter' instead, maybe the device concerned doesn't support this variant of FNAME$, I'm really not sure. I remember looking at this back in 2013 and was unable to resolve the issue reliably.Outsoft wrote:I got the same problem on my Trump Card to now trying to test QTRANS on my Winnybelg4rion67 wrote:Hi guys, I try to use PE on my QL with trump card 2 and qimi interfaces and things seems to go fine but I've some troubles with qtrans program: it starts but after it design screen with menus and buttons it displays this error:
qtrans_error.jpg
My system has two floppy drives and before launch qtrans I have configured it to use in right panel flp1_ and in left panel flp2_ but in another snap you can see that it not accept my configs
qtrans.jpg
Can somebody give me a tip to resolve?
Thanks
Paolo
When I get time I'll look at it again to see if there's a different way I could write the code to work around it, as with anything at the the moment TIME is the big problem.