LnS understanding rules

Discussion in 'LnS English Forum' started by Bovisa, Sep 7, 2008.

Thread Status:
Not open for further replies.
  1. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,353
    Location:
    France
    I'm not sure to understand properly your post.
    Which version of Look 'n' Stop are you using ?

    Do you mean the #1 in the title appears only when you manually quit/restart Look 'n' Stop, but it doesn't appear just after the boot for the very first time Look 'n' Stop is started for the Windows session ?

    When you quit Look 'n' Stop after having modified the ruleset and not having saved it, do you have a dialog box asking you if you want to save it now ? And if you have this dialog box, what is your answer (Yes, No, or Cancel) ?

    Thanks,

    Frederic
     
  2. Bovisa

    Bovisa Registered Member

    Joined:
    Sep 7, 2008
    Posts:
    18
    I have version 2.06p3. Yes, not on boot Windows, but when I manually quit and restart. When save dialog comes up I choose NO.

    I'm trying to get it now, but it doesn't happen anymore. But this morning it did happen again (2nd time).
    Well let's keep it hereby, but if it happens again I will comment.
     
    Last edited: Oct 14, 2008
  3. Phant0m

    Phant0m Registered Member

    Joined:
    Jun 7, 2003
    Posts:
    3,726
    Location:
    Canada
    Hi Bovisa,

    Best way to undo unsaved changes is to re-load the ruleset file instead of exiting and re-launching the Look 'n' Stop application.

    Are you using Vista 64-bit?


    Once in awhile I noticed when I manually exit out of Look 'n' Stop and re-start, it'll show #1 in the titlebar .. I'm assuming something isn't being freed fully.
     
  4. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,353
    Location:
    France
    Hi,

    When quitting Look 'n' Stop, it can take several seconds to close the process properly (especially if there was some traffic and log processing at that time).
    If you start again Look 'n' Stop during that time, maybe it is considered as a second instance and the #1 appears (however normally a second instance opens only when there is "-mult1" on the command line, so this is strange).

    Next time you have to do that (stopping/restarting Look 'n' Stop manually), I suggest you look at the list of active process (with the task manager), and you check if looknstop.exe is still active. Then you can make two kind of tests:
    1- start Look 'n' Stop and confirm it starts with the #1
    2- wait for looknstop disappearing from the list of active process before restarting it, and confirm it starts properly

    Regards,

    Frederic
     
  5. Bovisa

    Bovisa Registered Member

    Joined:
    Sep 7, 2008
    Posts:
    18
    Hi Frederic :),

    I bought 2 licenses of Look 'n' Stop for my 2 computers in my home network.
    Thank you very much for this fine peace of software. :thumb:
    Also thanks for the great support so far.
    Of course I'll not hesitate to ask questions if needed.

    Regards,
    Bovisa :)
     
  6. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,353
    Location:
    France
    Thanks for your support :)

    Frederic
     
  7. Bovisa

    Bovisa Registered Member

    Joined:
    Sep 7, 2008
    Posts:
    18
    Hi Frederic,

    I did reboot my computer, and upon startup of Windows, I directly doubleclicked LnS icon (in system tray). Directly when Windows user environment displays and able to click, I clicked (In meantime windows is loading all apps). Then I got a BSOD immediately. Did this happen because of LnS?

    Maybe I need to send the crash dump file?
     
  8. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,353
    Location:
    France
    Hi Bovisa,

    Normally no, double-clicking the icon is Ok as soon as it is displayed, and it should not cause a system crash.
    Yes, you can send the Minidump to lnssupport@soft4ever.com.

    Thanks,

    Frederic
     
  9. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,353
    Location:
    France
    Hi,

    I've received the Minidump file, and Look 'n' Stop drivers are not involved in the crash. Windbg only refers to "ntkrnlpa.exe".

    Regards,

    Frederic
     
  10. Phant0m

    Phant0m Registered Member

    Joined:
    Jun 7, 2003
    Posts:
    3,726
    Location:
    Canada
    likely that some errant third-party device driver is at fault, and since it happened when trying to bring up the GUI .. I'll assume the good place to start is with the graphics drivers. Try downloading the newest graphic drivers for your computer and uninstall the previous drivers first and re-boot, .. then install the newest graphics drivers you had downloaded.

    You should switch temporarily from Mini dumps to Kernel dump in 'Startup and Recovery' - System \ Advanced System Settings, 'Advanced' TAB. And reproduce the crash and e-mail out the Memory dump file (%SystemRoot%\MEMORY.DMP), should be-able to track down the problematic driver.



    Regards,
    Phant0m``
     
  11. Bovisa

    Bovisa Registered Member

    Joined:
    Sep 7, 2008
    Posts:
    18
    I installed LnS on my other computer, but at install it mentioned that the LnS driver didn't pass the Windows-logo-test, which ensures compatibility. Then I could choose to proceed or stop. It runs Windows XP Professional SP2. What I also don't understand is when installing Visual C++ Runtime Libraries it's from SP1, why doesn't LnS use SP2 runtime dlls?
     
  12. Phant0m

    Phant0m Registered Member

    Joined:
    Jun 7, 2003
    Posts:
    3,726
    Location:
    Canada
    Simply because Windows has SP2 doesn't mean SP2 exists for Microsoft Visual C++ 2008, .. do you have a link for Microsoft Visual C++ 2008 SP2?
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.