Announcement

Collapse
No announcement yet.

TSR on June/13 - What is going on?!!!!!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Paul Purvis
    replied
    well,this problem just does not go away.
    even though i have the most update pb 3.5 for dos i still am having
    problems with tsr(s) not loading in memory.
    i am writing this to inform my valued friends on this forum.

    i have a problem with the date 04/16/2006 in windows 2000 pro inside the
    cmd prompt. i have not tried the command prompt as of yet.
    i am aslo running microsoft virtual pc 2004, i get serveral dates wrong in
    msdos 6.22 virtual machine,
    04/18/2006, 04/19/2006, and a few dates i will post later, within 24hours.

    here is how i did my testing.
    i retreived the program tsrmark tsrremv off the internet.
    when tsrmark is run, it will place a marker in memory, actually a tsr program.
    when tsrremv is run, it will remove all tsr programs after the mark.
    i run tsrmark, my tsr, then mem/c > mem.prn, then search mem.prn with
    a program i wrote to do a text search for my loaded tsr program.
    then if the search fails, i place the date of the tsr not loading in a log file.
    then run tsrremv to remove any and all programs(should just me my tsr program) from
    memory, then run the batch file again.

    actually my batch file includes all the instructions form the year jan 1992 to aug 2057
    here is an example of the repeated batch file instructions

    date 01-01-2006
    tsrmark
    mytsrprogram
    mem/c > mem.prn
    mytextsearch program that searchs the mem.prn for my tsr
    tsrremv
    (continue repeated lines above using each date in all years to august 2057)
    (last line is below)
    date 08-31-2057
    tsrmark
    mytsrprogram
    mem/c >mem.prn
    mytextsearchprogram
    tsrremv
    date ??-??-???? (todays date to rest your computer to todays date)
    if your programs load fine on all dates, you should try running a
    repeated loop on the dates i have provided to be problems dates.

    do not run any other programs will this is running or you will have problems
    with the dates stamps being wrong in many files on your computer.

    i have noticed there did not seem to be any problems with the years
    prior to 2000, although in my virtual pc, i did find about 3 or 4 dates
    in the year 2000 where tsrs would not load, but we have passed that point in history.

    hope this heads off some problems with you other people reading this
    that have tsr(s) written being run every day.



    ------------------

    Leave a comment:


  • Lance Edmonds
    replied
    There are no changes to the NAME command - the error number is based on the error returned by the O/S.

    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Keith Waters
    replied
    Thanks PB for the upgrade but I did notice that NAME aFile$ AS aFile$ now returns ERR = 70 if aFile$ exists whereas before it returned ERR = 58 (or am I dreaming).

    Keith Waters

    Leave a comment:


  • Lance Edmonds
    replied
    Yes it is an update to the compiler.

    However, I'd pick that the problem is unlikely to happen under OS/2 (it probably would have by now otherwise) as OS/2 'mimics' a much older variety of DOS (for lack of better terminology). The problem seems to have arisen with changes MS made to MSDOS in 'recent' times.

    Unloading TSR's under an OS/2 DOS/VDM is not something I've had any experience with...

    ------------------
    Lance
    PowerBASIC Support
    mailto:supp[email protected][email protected]</A>

    Leave a comment:


  • Mike Luther
    replied
    Lance ..

    Is this a revision of the PB 3.5 Compiler?

    I tried his example in a DOS-VDM session for OS/2. It didn't
    smash, but I never could unload the thing either... It may be
    that I'm doing something wrong ..

    ------------------
    Mike Luther
    [email protected]

    Leave a comment:


  • Lance Edmonds
    replied
    Aye! Thanks Eric!

    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Eric Pearson
    replied
    Post code = Zip code in the U.S.?

    ------------------
    Perfect Sync: Perfect Sync Development Tools
    Email: mailto:[email protected][email protected]</A>

    Leave a comment:


  • Lance Edmonds
    replied
    Ok folks, a fix is now available. Email a request with your PowerBASIC serial number and your post code, and we'll email it out to you ASAP.

    The problem (as I understand it), was due to the way recent versions of the DOS sub-system worked internally. POPUP SLEEP was checking some DOS flags and because of these changes, POPUP SLEEP was not able to function. The fix solves this problem.

    Thanks for your patience!


    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Keith Waters
    replied
    Lance

    My earlier post said problem had gone away. Actually, it had gone
    away in my office. On return from office I started my home machine
    and (panic) the problem was still there. I rebooted and problem
    had gone (phew). Come on PB, we must get to the bottom of this.

    Keith Waters

    ------------------

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Lance!

    The problem passed away today - at 9 in the morning it was there, now at 5 pm it has gone.
    I am very interested what was the cause and if there will be another June 13.

    Thanks
    Paul


    ------------------
    Paul Moritz
    Lederergasse 23/4/4
    1080 Wien
    Austria

    Leave a comment:


  • Heber Jorge da Silva
    replied
    Lance,

    I am still very worried about this problem. Today I have found that the problem persists in certain machines, which means that I will continue having complaints from my users and having nothing to say to them...


    ------------------

    Leave a comment:


  • Lance Edmonds
    replied
    I don't have an answer back from R&D yet, but I can confirm that the "problem" (whatever is actually causing it) only appears to affect PB/DOS TSR apps on certain machines.

    In my own tests, I duplicated the problem on my Win2K box (K266), but on my p133 machine running Win95a and on my old 486 laptop (in both pure DOS and under Win95a) it runs fine.

    I'll report any news I gather. Thanks for the feedback folks!

    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Keith Waters
    replied
    Richard

    For me, the problem had gone away this morning (presumably it
    went away at midnight). But the matter is still worrying.

    Keith Waters

    ------------------

    Leave a comment:


  • Guest's Avatar
    Guest replied
    First first post is correct, if you change to a different date, and then reboot. The problems clears it self.



    ------------------

    Leave a comment:


  • Keith Waters
    replied
    Yes, I got the same problem. On the morning of 13/6/2000 my PB3.5
    tsr programs didn't work. Then a collegue rang from my office to
    say they wern't working there. Someone planted a time-bomb, and
    it detonated yesterday. I trust PowerBASIC is taking the matter
    seriously.

    Keith Waters

    ------------------

    Leave a comment:


  • Guest's Avatar
    Guest replied
    I got the same problem.
    The error appears only on Windows 95 and 98 computers in the DOS Box.
    In a pure DOS environment (DOS 6.22) it runs fine.
    It's very urgent, since my customer does all his data aquisition on the workfloor with this progam.

    Thanks
    Paul


    ------------------
    Paul Moritz
    Lederergasse 23/4/4
    1080 Wien
    Austria

    Leave a comment:


  • Lance Edmonds
    replied
    I'll Ask R&D about it and see what I can find out. Thanks!


    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Having the same problems but only on some machines. Other Machines appear to be working file. I tried changing the date forward but it made no difference.

    ------------------

    Leave a comment:


  • Heber Jorge da Silva
    started a topic TSR on June/13 - What is going on?!!!!!

    TSR on June/13 - What is going on?!!!!!

    H E L P ! ! !
    Does anyone know why any PB TSR program returns an error "5 - illegal function call" when the line POPUP SLEEP is executed - ONLY TODAY (JUNE 13). I have a TSR program developed in PB-DOS 3.30 with almost 3,000 users. Today 6/13/2000 our support team reported a huge amount of people complaining about this error. After checking the problem in our lab, we have discovered that:

    - The problem appears in any simple TSR program.
    - By changing the system date (forwards or backwards) and rebooting the computer, the error does not occur any more. It appears only if the system date is June 13!
    - This error occurs on Windows 95, Windows 98 and Windows 2000 but not on Windows NT-4 (???)
    - We have checked for viruses using several tools and found that our machines are clean!
    - We have compiled it with all PB-DOS versions (from 3.00 to 3.50) and the error persists!

    What is going on?! Is it an unknown Y2K bug affecting PB-DOS? Should it be a virus? If anyone wants to try, this little TSR may be compiled and run under the conditions above.
    So far, all I have to do is to tell my users to change the system date and reboot, before run my program

    '==============================
    'PowerBasic 3.5
    $COMPILE EXE
    $LIB IPRINT OFF, COM OFF
    $OPTION CNTLBREAK OFF
    $STRING 8
    DEFINT A-Z

    %AX=1
    %BX=2
    %CX=3
    %DX=4
    %SI=5
    %DI=6
    %BP=7
    %DS=8
    %ES=9

    CLS
    Par$=LTRIM$(RTRIM$(UCASE$(COMMAND$)))
    IF INSTR(Par$,"/D") THEN
    REG %AX, &HFF
    CALL INTERRUPT &H97
    END
    END IF
    POPUP KEY CHR$(8,46,115) 'ALT-C "hot key"
    POPUP INTERRUPT &H97, 10, OFF, OFF
    POPUP MULTIPLEX 253,253
    REG %AX,253
    REG %DX,253
    CALL INTERRUPT &H2F
    IF REG(%AX)<>253 AND REG(%DX)<>253 THEN END

    d&=SETMEM(-700000)
    PRINT "ALT-C to activate. Type ERROR /D to quit."

    WHILE 1 = 1
    REG %AX, 252:REG %DX,252
    POPUP SLEEP USING EMS, "c:\capt.swp"
    Ax=REG(%AX)
    IF Ax=253 AND REG(%DX)=253 THEN
    PRINT "Already installed..."
    PRINT "ALT-C to activate. Type ERROR /D to quit."
    PRINT""
    ITERATE
    END IF

    IF Ax=255 THEN
    POPUP QUIET OFF
    POPUP INTERRUPT OFF
    POPUP TIMER 1
    nSeconds=0
    WHILE nSeconds < 4
    POPUP SLEEP
    IF POPUP(1) THEN
    PRINT:PRINT "Unloaded from memory."
    END
    END IF
    INCR nSeconds
    LOOP
    ITERATE
    END IF
    CLS
    PRINT "ALT-C pressed."
    WEND
    END

Working...
X