Yes, there are many of us who might be able to fix this but we're missing the most important part.  None of us have the necessary permissions to edit Conover's scripts in the HUD nor access to the code in the PC program.   

"If you have modifiable source, you can modify the HUD to put out its full URL instead of just the key, and modify the controller to use that URL instead of constructing one using a fixed domain and that key."

He's saying:

1. The hud tells you the URL to use to connect to it from your PC, but it doesn't include the domain name which changed when SL was ported over to ACS (Amazon) which has a different domain from the former LL servers in Arizona.

2. The PC program assumes a domain name that was correct before (the old LL server domain) and isn't now. 

3.  It would probably be a fairly easy fix (change the hud to send it's full NEW URL) and change the controller to input the entire URL including the domain name then they would (presumably) be able to connect.  

4. We can't do either of those things because we can't edit the HUD script and we don't have source code for the PC program.

If I could find Mr Conover (assuming he's still alive somewhere) I'd offer him a lot of money to fix this. There's no other program that does this nor one as useful to me as his was.

Terry D.

From the LL guy on the forum link I posted:

"It's peripherally related.

That product uses a HUD in the target region. When rezzed, the HUD provides a UUID key that you need to enter into the controller program on your PC. That key is part of the URL for the HUD, but the domain name part of that URL has also changed.

If you have modifiable source, you can modify the HUD to put out its full URL instead of just the key, and modify the controller to use that URL instead of constructing one using a fixed domain and that key. If you don't, then I'm afraid it's permanently broken."

Terry D.

What a fantastic product that was!  Pity that nothing else available comes close to it.  :(

I looked hard for him too. I even checked obituaries. Fortunately I didn't find him in the latter.

I talked to Linden Lab people about this problem. They told me it would probably be a simple fix for someone with access to the source code. The problem is that when SL was moved to Amazion Cloud Services, the DNS server address would need an extra few digits on the front. Here's a link to the LL forum about it:

https://community.secondlife.com/forums/topic/460866-lsl-http-changes-coming/page/2/#elControls_2243114_menu

I looked hard for him too.  I even checked obituaries.  Fortunately I didn't find him in the latter.

I talked to Linden Lab people about this problem.  They told me it would probably be a simple fix for someone with access to the source code. The problem is that when SL was moved to Amazion Cloud Services, the DNS server address would need an extra few digits on the front.  Here's a link to the LL forum about it:

https://community.secondlife.com/forums/topic/460866-lsl-http-changes-coming/page/2/#elControls_2243114_menu

See this forum thread for LL's reply to why the scanner no longer works.  

https://community.secondlife.com/forums/topic/460866-lsl-http-changes-coming/page/2/

So what can be done about that, nothing?   Quite a useful program, such a shame.

Is Thomas still around?  Does anyone have the source code?  LL says the IP address needs to be different now to match the Amazon servers.

DNS usually refers to domain name system.  I'm guessing (just a guess) that the scanner connected to the web, either belonging to Thomas or SL.  Since Thomas has been gone much longer than the few months ago it stopped working, probably SL changed something that the scanner needed to work.