Jump to content
Light-O-Rama Forums

DevMike

Administrators
  • Content count

    3,539
  • Joined

  • Last visited

  • Days Won

    67

DevMike last won the day on November 4 2015

DevMike had the most liked content!

Community Reputation

429 Excellent

2 Followers

About DevMike

  • Rank
    LOR Developer

Profile Information

  • Gender
    Not Telling
  • Location
    Toddonia
  • Occupation
    Code Monkey

More About Me

  • How I learned about Light-O-Rama -
    I work here...
  • Favorite Decorating Holiday?
    .

LOR Software

  • LOR Software Version
    A Beta Version
  • License Level
    Pro

Recent Profile Visitors

3,960 profile views
  1. LOR S4 and Windows 10 issues

    JohnMcK - I would still like to review your helpdesk interaction. Please PM me your ticket number. Thanks!
  2. LOR S4 and Windows 10 issues

    For the OPs issue: Many things can cause that conversion to fail. The two most common are badly encoded files (which have been discussed) and permissions problems. If the SE can't get access to it's internal files, say because you installed the software under user "A" and are now trying to use the software with user "B" who does not have Windows Permissions to read the internal files created by "A", you will see that same error. The easy solution is to always use the same user account when using the LOR software as the one you installed it with. Alternatively, you can move the LOR Data files to the 'Public Documents' folder ( you will need to run LOR Post or Re-install to do that). You could also grant the correct permissions to the other user. What I am most concerned with however is that you say you asked us for help and got no results. Please post or PM me your help desk ticket so I can look at your issue. ------ JR: I think you and I talked about this before, and something tells me that I may have already posted something like this somewhere else. But this is a good place to give some info... I absolutely 100% believe you when you say 4.3.18 fixes it and 4.3.24 is broken. I am not blaming you or in any way trying to belittle or berate. If I could find something to fix the issue I would. I know exactly where you are coming from. If I didn't know as much as I do about programming Windows I would be on your side. But since I've been doing this now since DOS 2 I have gone through the differences between 4.3.18 and 4.3.24 many times. While I don't doubt that you are having an issue with 4.3.24 and 4.3.18 seems to fix it, I don't see anything in there that we changed. On the other hand, I can think of multiple different things that go wrong in Windows itself that would cause that to happen. For example, if one of our DLLs is somehow 'stuck' (technical term for something is borked in the registry that is preventing an old DLL from being completely removed. Borked is also technical.) on the 4.3.18 version, weird things could happen in 4.3.24. Going back to 4.3.18 changes the references/DLLsignature/DLL itself back to 'the stuck' 4.3.18 DLL and all is right again. I understand the frustration -- to you the end user, if 4.3.24 don't work and 4.3.18 does, then there is a problem with 4.3.24. Pretty simple -- what has changed is where the issue is and in 9 out of 10 cases you would be correct. But what many forget is that Windows is CONSTANTLY changing it's environment. Not just with updates (which are obvious), but by simply having the computer on. Indexing is occurring, background processes start and stop. Don't believe me? Disconnect your computer from the internet. install a fresh new copy of Windows on the computer. Don't do ANYTHING else. Leave it on for a day, a week, a month. During that time watch the HDD activity light. It blinks. blinking = windows is doing something, which in turn can be making changes to the registry, OS files, logs, etc. While 99.995% of the time those changes amount to a hill of beans, that .005% does come up and bite us -and it's completely outside of our control. FYI: We do get these types of problems from time to time. There is one thing that will fix them, and I absolutely HATE to give this answer - even if I know it will fix the issue: Reformat the computer. Since the start of computer help desks (not just ours), companies have used that 'fix' to just get you off the phone. They know that is a large undertaking (sometimes a couple of days to get things completely back together), or that you have so much stuff on your computer you won't do it. All those 3rd world help desks ruined this solution by OVER using it, but at some point Windows will get SO polluted the only thing to do is clean it out. (Yes: It happens to me. Yes, I reformat)
  3. Hi Joel, I approved your first message, but I am not sure if you are going to get the answer you need here as it sounds like you are not using our equipment (or any equipment that our users have - with the exception of 2812 pixels)
  4. Quick note: I know it says this in my signature, but if you are like me you tend to ignore signatures... Remember that forums are here for peer to peer help. They are a great resource. BUT if you need official LOR help for anything, PLEASE open a help desk ticket. Opening a help desk ticket ensures that you will get the answer you need, and allows us to track issues much more efficiently. We do monitor the forums and try to answer questions, but the official written way to ask us for support is through the help desk. Private Messages and posts are easily missed by us and may not be actively monitored, while the help desk is staffed. (Edit: Sorry!!! I just took the time to re-read what I posted last week and had to change it. I didn't realize that what I had said made it look like I was telling you not to post on the forums AT ALL! That is not what I meant to say. Please, by all means post here in the forums to get help from your fellow users. They are a wealth of knowledge, and sometimes know better ways to use the software/hardware than even us!. If however you need 'official' tech support, sales support, etc. please don't PM me or any of the other LOR mods/devs/etc. Instead, open a help desk ticket so we can properly track the issue and get you squared away. The only exception to this rule is for beta releases of the software: For those, please post in the appropriate msg board.)
  5. Goodbye Tor

    Tor we hardly knew you! After many years as part of the LOR family, Tor has decided to move on to a new opportunity. As we said before, Tor was involved with LOR from the start, and his loss will be felt for some time. We wish him all the best luck in the future and thank him mightily for all he has given to us! Go get em Tor!
  6. Fire at LOR

    No actually it sounds like one of the neighbors did not dispose of his rags properly and they spontaneously combusted. Please remember that oily/solvent soaked/etc rags should be disposed of in a fire safe can with a lid. Placing them outdoors on a flat non flammable surface works too. (I knew those IA classes I had 35 years ago would pay off!)
  7. Many people overnight have received a private message from a user called 'Jose' asking for help with the LOR software. While we are unsure if the messages are a scam/phish/etc (it may be that things are just being lost in translation), please do not reply to them. We also have multiple reports, so there is no need to report them again - simply delete the PM for now. As with anything else on the internet, please -- NEVER share personal information with people you do not know.
  8. Fire at LOR Factory in Glens Falls

    1/18/2018 10:20 AM We are experiencing intermittent issues with our data/phone connections at this time. Phones may not be available until this is resolved. We have contacted our provider.
  9. Fire at LOR

    We looked at it the same way. In case you did not see the announcement - the utilities were turned back on late last night. We have started to resume operations. Things may be a little slower than normal today as we ramp back up, but other than that you can expect business as usual from us.
  10. Fire at LOR Factory in Glens Falls

    1/18/2018 9:30AM Late last night utilities to the building where turned back on. For the rest of the day today we expect to ramp back up operations. We expect to be fully operational by tomorrow. Again, just to reiterate: We are back to full functionality. All departments that were closed are now open. We have resumed normal operations.
  11. Fire at LOR Factory in Glens Falls

    More news: http://poststar.com/news/local/investigators-link-fire-to-spontaneous-combustion-in-moreau/article_f5f018bc-b733-5278-a183-ae664ee2f337.html https://dailygazette.com/article/2018/01/16/firefighters-scramble-to-south-glens-falls-fire
  12. Fire at LOR Factory in Glens Falls

    LOR would like to extend its appreciation and thanks to everyone involved in containing the fire and moving as quickly as they did. We are all very happy to hear that no one was injured, responders and tenants alike. Multiple fire companies responded to the call and fought the fire in what can be described as very challenging conditions including the location, cold and snow. To the firefighters we say thank you for everything you do. The NYS Troopers as well as the Saratoga County Sheriff department also responded, and to them we also extend a thank you for keeping everyone safe. We apologize if you were involved and not named directly. Because of the scope of the incident, we just don't know everyone that was involved. To you we extend a hardy "Thank You!" To our neighbors in the building who did suffer losses to their businesses, please accept our sincere sympathy during this trying time. Please let us know if there is something we can do to help. We will do our best to help out where we can.
  13. Fire at LOR Factory in Glens Falls

    News: http://poststar.com/news/local/flames-rip-through-moreau-complex-updated/article_88e85dff-51bd-5ac3-b4c1-6283b1db3766.html#tracking-source=home-top-story http://cbs6albany.com/news/local/multiple-fire-crews-rush-to-saratoga-county-fire (thanks Smithzone) https://dailygazette.com/galleries/2018/01/16/south-glens-falls-structure-fire-chase-sports (thanks Smithzone)
  14. Fire at LOR Factory in Glens Falls

    Update 2: 9:30 AM Minimal to no Damage. After what you can imagine was a nearly sleepless night, we have been able to access our part of the building. Other than a slight smoke smell, and a door that was broken down (most likely by the FD) there is no damage to the LOR facilities. Everything and more importantly everyone is safe. While we may not have suffered any real damage, the fire will affect our operations. All of the utilities are either shut off or damaged. That means we have no electricity, no heat, and no data. Restoring these utilities may take some time, due to inspections that need to be done, restoration of damage, etc. We don't expect it to take too long, but we don't have any ETA at the moment. We are in the process of updating all of our systems to let folks know what is happening. As of right now the following are closed/suspended/in process of being shut down: Manufacturing Ordering/Online Store Order Fulfillment Repairs Returns Phone Support/Phone Ordering Receiving is currently running in a VERY LIMITED capacity. Please hold ALL shipments to us (such as for repairs or returns) if possible - even if you have received an RMA from us. We will of course extend our 30 day and product warranties that fall inside of this down time. RMAs will still be good once we restart operations. On-Line support is up and operational, however please expect delays.
×