Re: [Ql-Users] DM5 upsetting Dates in QPC2
On 30/06/17 04:06, Wolf via Ql-Users wrote:
Hi,
There seems to be 2 differences between PAUSE and WAIT.
PAUSE needs channel #0, WAIT doesn't.
True
PAUSE can be interrupted with a keypress, WAIT can't.
True
Wait comes from the outptr toolkit (on my QLStuff webpage, pointer
tools). It just suspends the calling job for x ticks : WAIT x
You can replace it with Pause - or even a simple delay loop if you want
to run it without windows pen (in the case of Pause).
FYI, on my machine runing SMSQmulator, the timings of the p procedure
would look as follows:
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 REMark WAIT 20- not used !
140 HOT_DO('g')
150 WAIT 1
160 HOT_DO('g')
170 WAIT 1
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Have fun!
Wolfgang
___
QL-Users Mailing List
Hi Wolfgang,
Thank you for the explanation, I forgot about your excellent OUTPTR Toolkit.
I tried your example the parameters entered in the WAIT command seem to
allow the Invalid Date to be sort of by-passed.
Do you think the DM5_OBJ programme can be patched to not check the
system date?
I was asked in a Private Message in the QL Forum how to run DM5,
personally, I would not use it too many issues to correct.
I like to use Cue-Shell, could this be released as freeware?
--
Regards,
Derek
___
QL-Users Mailing List
[Ql-Users] DM5 upsetting Dates in QPC2
Hi,
There seems to be 2 differences between PAUSE and WAIT.
PAUSE needs channel #0, WAIT doesn't.
True
PAUSE can be interrupted with a keypress, WAIT can't.
True
Wait comes from the outptr toolkit (on my QLStuff webpage, pointer
tools). It just suspends the calling job for x ticks : WAIT x
You can replace it with Pause - or even a simple delay loop if you want
to run it without windows pen (in the case of Pause).
FYI, on my machine runing SMSQmulator, the timings of the p procedure
would look as follows:
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 REMark WAIT 20- not used !
140 HOT_DO('g')
150 WAIT 1
160 HOT_DO('g')
170 WAIT 1
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Have fun!
Wolfgang
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no matter in this case. Dilwyn has used a similar thing from my extensions to make a new Keyword to suspend a Job. The extension Ralf referred to here is called SUSPEND. Available on Toolkits page at http://www.dilwyn.me.uk/tk/suspend.zip Dilwyn ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Of course, as it is used to suspend the job.
Am 29.06.2017 um 19:48 schrieb François Van Emelen via Ql-Users:
Op 29/06/2017 om 17:11 schreef Ralf Reköndt via Ql-Users:
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing from my extensions to make a new
Keyword to suspend a Job.
Am 29.06.2017 um 12:58 schrieb Wolf via Ql-Users:
Sorry, yes it is.
On 29/06/2017 12:04, Derek Stewart via Ql-Users wrote:
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
Hi Wolfgang,
I do not have the keyword WAIT in my SMSQ/E v3.31, is that like
PAUSE ???
Hi,
There seems to be 2 differences between PAUSE and WAIT.
PAUSE needs channel #0, WAIT doesn't.
PAUSE can be interrupted with a keypress, WAIT can't.
François Van Emelen
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Op 29/06/2017 om 17:11 schreef Ralf Reköndt via Ql-Users:
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing from my extensions to make a new
Keyword to suspend a Job.
Am 29.06.2017 um 12:58 schrieb Wolf via Ql-Users:
Sorry, yes it is.
On 29/06/2017 12:04, Derek Stewart via Ql-Users wrote:
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
Hi Wolfgang,
I do not have the keyword WAIT in my SMSQ/E v3.31, is that like
PAUSE ???
___
QL-Users Mailing List
Hi,
There seems to be 2 differences between PAUSE and WAIT.
PAUSE needs channel #0, WAIT doesn't.
PAUSE can be interrupted with a keypress, WAIT can't.
François Van Emelen
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing from my extensions to make a new Keyword
to suspend a Job.
Am 29.06.2017 um 12:58 schrieb Wolf via Ql-Users:
Sorry, yes it is.
On 29/06/2017 12:04, Derek Stewart via Ql-Users wrote:
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
Hi Wolfgang,
I do not have the keyword WAIT in my SMSQ/E v3.31, is that like PAUSE ???
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Sorry, yes it is.
On 29/06/2017 12:04, Derek Stewart via Ql-Users wrote:
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
___
QL-Users Mailing List
Hi Wolfgang,
I do not have the keyword WAIT in my SMSQ/E v3.31, is that like PAUSE ???
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
___
QL-Users Mailing List
Hi Wolfgang,
I do not have the keyword WAIT in my SMSQ/E v3.31, is that like PAUSE ???
--
Regards,
Derek
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
___
QL-Users Mailing List
Hi Wolfgang,
I suppose that is one way to get around the problem.
My supplementary question was is it worth writing this type of problem
from the DM5 usage. Since all the development software is now free.
Maybe worth an look and get more experience of Easypointer 4
--
Regards,
Derek
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.
Have fun
Wolfgang
___
QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
On 27/06/17 13:01, Marcel Kilgus via Ql-Users wrote: Derek Stewart via Ql-Users wrote: Does anyone know of any contact for PM_DATA, to see if the DM5 source code can be released, to correct the problem. He would if he could, but apparently he doesn't have the sources anymore. Marcel ___ QL-Users Mailing List Hi Marcel, I have just found a link in the QL Forum to the QL-USERS mailing List Archive: https://www.mail-archive.com/search?l=ql-users-q-v-d@lists.q-v-d.com&q=subject:%22Re%5C%3A+%5C%5Bql%5C-users%5C%5D+Disk+Mate+5%22&o=newest&f=1 indicating that the source code is lost. Looks like a good piece of software lost. -- Regards, Derek ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Derek Stewart via Ql-Users wrote: > Does anyone know of any contact for PM_DATA, to see if the DM5 source > code can be released, to correct the problem. He would if he could, but apparently he doesn't have the sources anymore. Marcel ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Hi, I have been looking at the problem with Disk Mate 5 on QPC2 & SMSQmulator and every time I load Disk Mate 5 I am prompted for the current date. Since the Year is only 2 digits this is causing a problem, since we are now in 2017. I think the programme must be thinking the date is 1917 rather than 2017. I reset my PC clock to 1999 and Disk Mate 5 started up correctly. Resetting the PC clock back to 2017 causes a problem with the date, I tried to email PM_DATA, but the email address in the DM5 Manual is unreachable. Does anyone know of any contact for PM_DATA, to see if the DM5 source code can be released, to correct the problem. Otherwise like most Year 2000 incompatible software, it is consigned to the bin, or maybe DM5 could be re-written from the screen functions??? -- Regards, Derek On 13/01/17 11:21, Bob Spelten wrote: Op Fri, 13 Jan 2017 06:41:10 +0100 schreef Wolf : Hi, there ae 2 versions of DM : DM5_obj and DM5_int_obj , the problem only seems to arise on the..int version, use the other one instead. Minor point is that only the _int_ version has been patched for GD2. I just installed both versions in SMSQm8 and both reported the date error but now my PC clock was not upset, nor by OK on the given date. There was a Qlib error next on "Q_ERR_ON"(?)- both versions and Qlib_run was installed - but a Continue did start the program. Then there was a running error on the FEX keyword, which is expected to be an FI2 command but may have been disabled while the SMSQ/E command does something completely different. To resolve both issues the sources are needed so I think it's wise to avoid DM5 until this is resolved. Earlier I had patched my copies of DM5 and FI2 to read FFX instead of FEX, which worked until the date problem arose. Bob On 12/01/2017 17:47, Martyn Hill wrote: Hi Bob Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw oddities around the date before it would hang QPC. I didn't investigate to the same depth, but it appears to match your experience. Martyn. On 12/01/2017 15:35, Bob Spelten wrote: Hi All, I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious problem. It reported a wrong date but while the suggested date was correct my PC clock had been reset in the background to 18-Jan-2053, causing problems on the W$7 side. In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. Also a previous QPC2 (v3.40/3.16) behaved the same. I have used DM5 for GD2 sporadically before but never seen this bug. Has something changed in SMSQ/E's date handling that is not working for DM5 anymore? Has anyone experienced this before? Bob ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Op Fri, 13 Jan 2017 06:41:10 +0100 schreef Wolf : Hi, there ae 2 versions of DM : DM5_obj and DM5_int_obj , the problem only seems to arise on the..int version, use the other one instead. Minor point is that only the _int_ version has been patched for GD2. I just installed both versions in SMSQm8 and both reported the date error but now my PC clock was not upset, nor by OK on the given date. There was a Qlib error next on "Q_ERR_ON"(?)- both versions and Qlib_run was installed - but a Continue did start the program. Then there was a running error on the FEX keyword, which is expected to be an FI2 command but may have been disabled while the SMSQ/E command does something completely different. To resolve both issues the sources are needed so I think it's wise to avoid DM5 until this is resolved. Earlier I had patched my copies of DM5 and FI2 to read FFX instead of FEX, which worked until the date problem arose. Bob On 12/01/2017 17:47, Martyn Hill wrote: Hi Bob Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw oddities around the date before it would hang QPC. I didn't investigate to the same depth, but it appears to match your experience. Martyn. On 12/01/2017 15:35, Bob Spelten wrote: Hi All, I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious problem. It reported a wrong date but while the suggested date was correct my PC clock had been reset in the background to 18-Jan-2053, causing problems on the W$7 side. In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. Also a previous QPC2 (v3.40/3.16) behaved the same. I have used DM5 for GD2 sporadically before but never seen this bug. Has something changed in SMSQ/E's date handling that is not working for DM5 anymore? Has anyone experienced this before? Bob -- The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/"; ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Wolf wrote: >> Do you think the source ocde could be released. > It would be nice, but I presume the author would aready have done so by now. Problem is, even the author doesn't have the source code anymore. Marcel ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Hi, I tried both and give the same date problem. Here, they both protest that the date is wrong, but only the ...int version crashes QPC, the other works OK.. The file Extensions_cde looks like it is DIY Toolkit extensions, Phil Borman's WIN Tools. Which I doubt have any problems. This Extensions_cde seems to add the following keywords: XSTAT XDSTAT TREE WDSTAT WDDIR WDDEL WDDEL_F NEWCHAN% LOOKUP% UPPER$ LOWER$ SORT I_FILL PDCODE BRK_OFF BRK_ON SET_POS PUTIN$ ANYOPEN% MSEARCH POKE_$ PEEK_$ INARRAY% GetHEAD SetHEAD In the updates_doc, there was an issue with v5.05 getting the months wrong, maybe the invalid date is connected to this. I'm not sure whether the date is really the problem, for two reasons: 1. You can set the date to something, in, say, 2005 - and it still crashes in QPC. 2. When the software tells you that the date is wrong, you can leave this window either with ESC or OK. When you leave it with ESC, the software does NOT try to set the date, so that isn't the problem either. But this maybe be a Year2000 issue. Probably not, we'd have noticed by now. Do you think the source ocde could be released. It would be nice, but I presume the author would aready have done so by now. Regards, Wolfgang ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Hi, I tried both and give the same date problem. The file Extensions_cde looks like it is DIY Toolkit extensions, Phil Borman's WIN Tools. Which I doubt have any problems. In the updates_doc, there was an issue with v5.05 getting the months wrong, maybe the invalid date is connected to this. But this maybe be a Year2000 issue. Do you think the source ocde could be released. Regards, Derek On 13/01/17 05:41, Wolf wrote: Hi, there ae 2 versions of DM : DM5_obj and DM5_int_obj , the problem only seems to arise on the..int version, use the other one instead. Wolfgang On 12/01/2017 17:47, Martyn Hill wrote: Hi Bob Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw oddities around the date before it would hang QPC. I didn't investigate to the same depth, but it appears to match your experience. Martyn. On 12/01/2017 15:35, Bob Spelten wrote: Hi All, I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious problem. It reported a wrong date but while the suggested date was correct my PC clock had been reset in the background to 18-Jan-2053, causing problems on the W$7 side. In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. Also a previous QPC2 (v3.40/3.16) behaved the same. I have used DM5 for GD2 sporadically before but never seen this bug. Has something changed in SMSQ/E's date handling that is not working for DM5 anymore? Has anyone experienced this before? Bob ___ QL-Users Mailing List ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Hi, there ae 2 versions of DM : DM5_obj and DM5_int_obj , the problem only seems to arise on the..int version, use the other one instead. Wolfgang On 12/01/2017 17:47, Martyn Hill wrote: Hi Bob Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw oddities around the date before it would hang QPC. I didn't investigate to the same depth, but it appears to match your experience. Martyn. On 12/01/2017 15:35, Bob Spelten wrote: Hi All, I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious problem. It reported a wrong date but while the suggested date was correct my PC clock had been reset in the background to 18-Jan-2053, causing problems on the W$7 side. In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. Also a previous QPC2 (v3.40/3.16) behaved the same. I have used DM5 for GD2 sporadically before but never seen this bug. Has something changed in SMSQ/E's date handling that is not working for DM5 anymore? Has anyone experienced this before? Bob ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Bill, Feeling fine now and traffic looks OK, so see you there. Dave. Sent from my iPad Pro Tel: +44 (0)1707 652791 Mobile: +44 (0)7999 218953 > On 12 Jan 2017, at 16:47, Martyn Hill wrote: > > Hi Bob > > Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw > oddities around the date before it would hang QPC. > > I didn't investigate to the same depth, but it appears to match your > experience. > > Martyn. > >> On 12/01/2017 15:35, Bob Spelten wrote: >> Hi All, >> >> I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious >> problem. >> It reported a wrong date but while the suggested date was correct my PC >> clock had been reset in the background to 18-Jan-2053, causing problems on >> the W$7 side. >> In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. >> Also a previous QPC2 (v3.40/3.16) behaved the same. >> >> I have used DM5 for GD2 sporadically before but never seen this bug. >> Has something changed in SMSQ/E's date handling that is not working for DM5 >> anymore? >> Has anyone experienced this before? >> >> Bob >> > > -- > "There are 10 types of people in this world. Those who understand binary and > those who don't." > > ___ > QL-Users Mailing List ___ QL-Users Mailing List
Re: [Ql-Users] DM5 upsetting Dates in QPC2
Hi Bob Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw oddities around the date before it would hang QPC. I didn't investigate to the same depth, but it appears to match your experience. Martyn. On 12/01/2017 15:35, Bob Spelten wrote: Hi All, I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious problem. It reported a wrong date but while the suggested date was correct my PC clock had been reset in the background to 18-Jan-2053, causing problems on the W$7 side. In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. Also a previous QPC2 (v3.40/3.16) behaved the same. I have used DM5 for GD2 sporadically before but never seen this bug. Has something changed in SMSQ/E's date handling that is not working for DM5 anymore? Has anyone experienced this before? Bob -- "There are 10 types of people in this world. Those who understand binary and those who don't." ___ QL-Users Mailing List
[Ql-Users] DM5 upsetting Dates in QPC2
Hi All, I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious problem. It reported a wrong date but while the suggested date was correct my PC clock had been reset in the background to 18-Jan-2053, causing problems on the W$7 side. In my QPC2/QLE this also froze SMSQ/E but not in my normal QPC2. Also a previous QPC2 (v3.40/3.16) behaved the same. I have used DM5 for GD2 sporadically before but never seen this bug. Has something changed in SMSQ/E's date handling that is not working for DM5 anymore? Has anyone experienced this before? Bob -- The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/"; ___ QL-Users Mailing List
