Thorium

[AstroSkipper]

Open these four registry keys with your registry editor and post here via the export feature of Registry Workshop (I know you are using the same tool as I do.  I need to know the exact strings in form of an exported key for better comparison ) what have been set for them in HKEY_CLASSES_ROOT\http, HKEY_CLASSES_ROOT\https, HKEY_CLASSES_ROOT\ThoriumHTM\shell\open\command and HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\Thorium\shell\open\command. Use the code feature of the forum editor for pasting the exported keys!

Edited August 9, 2024 by AstroSkipper
Update of content

[AstroSkipper]

3 hours ago, AstroSkipper said:

3 hours ago, Dave-H said:

Now I'm even more puzzled.

The reason why the Profile= line entry didn't have quotes around it was because it didn't have quotes around it in the original 360Loader INI file.

I've tried using your corrected code, and it doesn't work, Thorium runs but does not use the correct User Data folder, and creates a new one in D:\Program Files\Thorium\Chrome\Application\Default. It should be in D:\Program Files\Thorium\Chrome\User Data.

And I'm sorry but I have no idea what the 'Space Bug' refers to!
Sorry to be so thick.

Expand  

You are not thick. If at all, a little forgetful.  We had the problem back then in the beta test of my ProxHTTPSProxy package. I called the problem the "space bug". Search my proxy thread for "space bug"! Normally, if a space is inside a path, the string needs quotation marks when it comes to coding. Especially when using command line commands or programming batch files. Maybe, this loader allows such spaces when defining variables. Personally, I have no spaces in my user folder for Thorium. So, I have no problems with that. Long story short. Just remove the quotation marks in the line where the $Profile$ variable is defined! But what about my questions? 

So, I have checked this, and you are right.  No quotation marks are necessary for defining a variable if it contains spaces. A bit strange, though. I wouldn't have thought so. 

[AstroSkipper]

1 hour ago, Dave-H said:

And if I try to open a page, even an internal one like the settings page, I get this -

Can you describe the quoted issue more detailed? You can't open internal pages or the setting page in Thorium? Did I understand you correctly? 

[Dave-H]

That's correct, no pages will open at all, even internal ones like settings. They just crash.

Here's the registry keys' contents you asked for.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\http]

[HKEY_CLASSES_ROOT\http\AnimExtensions]
"."="dxmasf.dll,150"
".asf"="dxmasf.dll,150"
".asp"="dxmasf.dll,150"
".asx"="dxmasf.dll,150"
".nsc"="dxmasf.dll,150"
".wax"="dxmasf.dll,150"
".wm"="dxmasf.dll,150"
".wma"="dxmasf.dll,150"
".wmv"="dxmasf.dll,150"
".wmx"="dxmasf.dll,150"
".wvx"="dxmasf.dll,150"

[HKEY_CLASSES_ROOT\http\Extensions]
".mka"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".mkv"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".webm"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".mp4"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".mov"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".3gp"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".oga"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".ogg"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".ogm"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".ogv"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".ts"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"
".m2ts"="{B98D13E7-55DB-4385-A33D-09FD1BA26338}"

[HKEY_CLASSES_ROOT\http\shell]

[HKEY_CLASSES_ROOT\http\shell\open]

[HKEY_CLASSES_ROOT\http\shell\open\command]
@="\"D:\\Program Files\\Thorium\\ThorLoad.exe\" \"%1\""

[HKEY_CLASSES_ROOT\http\shell\open\ddeexec]

[HKEY_CLASSES_ROOT\http\shell\open\ddeexec\Application]
@="Thorium"

[HKEY_CLASSES_ROOT\http\shell\open\ddeexec\Topic]
@="WWW_OpenURL"

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\https]

[HKEY_CLASSES_ROOT\https\shell]

[HKEY_CLASSES_ROOT\https\shell\open]

[HKEY_CLASSES_ROOT\https\shell\open\command]
@="\"D:\\Program Files\\Thorium\\ThorLoad.exe\" \"%1\""

[HKEY_CLASSES_ROOT\https\shell\open\ddeexec]

[HKEY_CLASSES_ROOT\https\shell\open\ddeexec\Application]
@="Thorium"

[HKEY_CLASSES_ROOT\https\shell\open\ddeexec\Topic]
@="WWW_OpenURL"

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\ThoriumHTML\shell\open\command]
@="\"D:\\Program Files\\Thorium\\ThorLoad.exe\" \"%1\""

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\Thorium\shell\open\command]
@="\"D:\\Program Files\\Thorium\\Chrome\\Application\\Thorium.exe\" \"%1\""

As you can see, I've called the loader file 'ThorLoad.exe'.
This is its entry in StartMenuInternet.
I didn't generate that, the system presumably did.
It has no '%1' at the end for some reason.
 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\ThorLoad.exe\shell\open\command]
@="\"D:\\Program Files\\Thorium\\ThorLoad.exe\""

[AstroSkipper]

@Dave-H The strategy I would like to recommend to you is to set the browser settings in your Windows XP installation back to Internet Explorer as default browser. Open the Internet Explorer options and set it as your default browser! After doing so, remove all entries related to Thorium using Registry Workshop! Search for Thorium and ThorLoad! The reason for this strategy is that I assume something browser related has been messed up. It is difficult to find the error as there are many registry keys in terms of registering a browser and its corresponding extensions. Revert everything you tried to make Thorium as your default browser! I have seen you are using the SSE4 release. Does it work properly in your system?  Maybe, you could give the SSE3 release a try only to see if it is working better than the SSE4 one. Just an idea, of course! You know the higher is not always the better.  In any case, be careful when purging your registry!  Perform a registry backup first!  Everything else after that. What do you think about this approach? 

Edited August 10, 2024 by AstroSkipper

[Dave-H]

Thanks.

What I was thinking of doing, as I still have Google Chrome 49 installed on the XP system, and it does have the mechanism to make it the default browser, is to try making that the default browser temporarily, check that works properly with links, and then go through the registry changing all of its entries to point to Thorium instead.
Does that sound like a plan?

 

[Dixel]

11 hours ago, Dave-H said:

Does that sound like a plan?

Old chrome had 

--user-data-dir="...\data"

instead of 

--user-data-dir="..\data"

I don't remember exactly.

 

[Dave-H]

Thanks, I'll bear that in mind!
I was just thinking that making another Chromium browser the default, even a very old one, would be a better starting point than doing it with Internet Explorer.

[AstroSkipper]

1 hour ago, Dave-H said:

Thanks.

What I was thinking of doing, as I still have Google Chrome 49 installed on the XP system, and it does have the mechanism to make it the default browser, is to try making that the default browser temporarily, check that works properly with links, and then go through the registry changing all of its entries to point to Thorium instead.
Does that sound like a plan?

 

1 hour ago, Dave-H said:

Thanks, I'll bear that in mind!
I was just thinking that making another Chromium browser the default, even a very old one, would be a better starting point than doing it with Internet Explorer.

You can make any other browser, which has already properly been installed in your system, the default, of course. Important is to get rid of everything related to Thorium. When done, check if the old Chromium correctly works as your temporary, default browser.

Edited August 10, 2024 by AstroSkipper

[AstroSkipper]

@Dave-H If your plan doesn't work, consider my strategy then. The steps are necessary for further steps I wanted to perform.  And I don't know whether they work with an old Chrome as default. The Internet Explorer is automatically set as default browser by Windows XP if no other has been set by the user.

Edited August 10, 2024 by AstroSkipper
correction

[Dave-H]

Thanks, it will be in a while now, but I will report back!

 

[AstroSkipper]

Now, a question to all who are running Thorium under Windows XP Professional SP3 with all updates after SP3 but without any POSReady updates. Does Thorium work under these conditions?  I have two Windows XP installations, one with and one without POSReady updates. When I start Thorium on Windows XP without POSReady updates, it crashes randomly without any messages. With crashing I mean a sudden closing of the browser without any actions by me, either directly when starting the browser or seconds respectively minutes later. 

Edited August 10, 2024 by AstroSkipper
Update of content

[NotHereToPlayGames]

16 minutes ago, AstroSkipper said:

Now, a question to all who are running Thorium under Windows XP Professional SP3 with all updates after SP3 but without any POSReady updates. Does Thorium work under these conditions?

Yes.  Thorium works great for me in XP x86 SP3, fully updated, without POSReady (you already know my "view" on POSReady, wink wink, it "killed" a past XP machine with several CAD programs, forced a complete reinstall, have never touched POSReady since).

On all three of the following  --  Single-core VM.  Dual-core real hardware.  Single-core Intel Atom.

Also works great in XP x64 SP2, fully updated, unsure if POSReady is even "for" x64 (never tried POSReady in x64, never will).

 

I actually have the exact opposite experience with Supermium.  Crashes or won't even launch for me.  Only tried it on my single-core Intel Atom and in single-core VM.

[NotHereToPlayGames]

53 minutes ago, AstroSkipper said:

Now, a question to all

Since you edited to add bold and underline.

You may want to consider that I am very likely the ONLY member of MSFN that runs XP (both x86 and x64), both in VM and real era-correct hardware (slower performance than yours, as I recall), that does NOT install POSReady.

[AstroSkipper]

16 minutes ago, NotHereToPlayGames said:

Yes.  Thorium works great for me in XP x86 SP3, fully updated, without POSReady (you already know my "view" on POSReady, wink wink, it "killed" a past XP machine with several CAD programs, forced a complete reinstall, have never touched POSReady since).

On all three of the following  --  Single-core VM.  Dual-core real hardware.  Single-core Intel Atom.

Also works great in XP x64 SP2, fully updated, unsure if POSReady is even "for" x64 (never tried POSReady in x64, never will).

 

I actually have the exact opposite experience with Supermium.  Crashes or won't even launch for me.  Only tried it on my single-core Intel Atom and in single-core VM.

Thanks for replying! And yes, I know very well your opinion about POSReady updates for Windows XP.  But on my computer, Thorium only works in my Windows XP system with all POSReady updates. Maybe by accident, and there is another causer for my described issue. That's all a bit strange.  Are there any specific requirements for Thorium in terms of system software, especially regarding runtime libraries and so on?