The store button flashes the current settings into the unit for stand-alone mode usage. This has nothing to do with 'system settings'. So what exactly is the problem that you see?

We are not working on the driver at this time as we are not aware of any bug caused by us.

Post 7 and 10 of that thread:
Go to the About tab of the Settings dialog and toggle the Lock Registry checkbox.

I don't see what a different FireWire system driver has to do with our settings dialog trying to write entries into the registry (or reading them), where that system driver is not involved at all. That points to a screwed up Windows installation, more than anything else. If you have some Windows knowledge you could easily check and verify the current settings within the registry by using regedit. They are easy to find.

@funkyspacecadet
Thank you for supporting my point :-)
IMHO some more thought should be given to this problem which, as I mentionned above, has already been discussed in this forum. My windows installation is as clean and fresh as it could be. These problem I'm having have started right after my upgrade to Windows 8 from Windows XP (a clean re-install of all my system and applications).

@MC
I'm not in the recording studio this weekend. Will check the registry for "faulty" Fireface settings if any. Are there in the same place as the "registry lock" password?

One suggestion occurred to me: with so many people having trouble with Windows 8 firewire new driver and Microsoft been not likely to amend it soon or ever, it would certainly a great benefit for us, users, if RME and Thesycon, both companies based in Germany I guess, could cooperate to offer us a real fix. For example, it would be nice if RME could issue a brief doc explaining what are the best parameters for an optimal Fireface/Thesycon cooperation. Unless I've missed something already explained here or on Thesycon website?
Maybe an idealistic musician view?

Best,
Bob

Yes. After changing a setting in the dialog just refresh the view of regedit and the changed parameter should be seen there as well.

I can not share this statement. Most customers have no FW problems under W8 (including ourselves), although - just an example - I am using an outdated, not recommended Ricoh chip. It seems to us that most customers complaining now have a basic hardware problem that had been there before (solved by using the legacy driver under W7), which we can not fix.

Regarding your problem: checking the registry you would see if changes in the Settings dialog cause changes in the reg entries. If not then they are not written. If yes reboot and check if the are still the same. If so then the read process upon boot fails.

That could also be a rights problem. W8 has some new restrictions and different methods to before, making ones life as single admin user even more complicated. I have not tested W8 with a normal user account with restricted rights. We expect a DAW user to be the owner of his machine, means admin. Note that the super admin mode is not required.

How does using the legacy driver solve a "basic hardware problem" ?

Also the requirement for the legacy driver is nothing new, this dates back to Vista and it seems many, many people using all kinds of FW hardware have the same issue. 

So if there is a way to make things work with the standard driver, what must we do?

I have done many clean installs on my two PCs I've used the FF400 with.  Before installing anything like antivirus, any other software I still had the same issue, with High Performance power profile enabled, with CPU scaling disabled to keep my CPU at it's max speed.  On two VIA chipsets and now a TI one.

The above with Win7 and Win8.

Perhaps I should see if I can borrow another FW interface to see if it doesn't happen with that?

Win8's admins tuff is a bitch!   However the legacy driver doesn't seem to have any problems with saving/restoring the settings, only the legacy driver.  ie: I've changed buffer sizes and other things many times with the legacy driver and that's fine, providing I don't change back to the standard driver or forget to boot with driver signing disabled as I described in Scenario 2.

I have UAC disabled and I have admin rights.

Thanks MC.

Excuse me?

Thanks MC for your suggestion. I'm now back in the studio and I've been trying to apply your suggestions. The problem of loosing Fireface settings upon reboot can be narrowed down to Windows 8's admin rights management, as actually no Fireface settings except the password are recorded in the registry. Totalmix Registry values are there and updated but it's not the case with fireface settings except the "lock regsitry" password.

Amen to that. According to my findings, Windows 8 gives you almost admin rights but not the full admin access to your machine (like in XP or Seven). I will have to dig further into that...

Now concerning my second topic, I have the pleasure to say that the legacy OHCI driver is working nicely, perfectly in fact :-)

@funkyspacecadet
I've been lucky: I didn't even have to deal with any unsigned driver problem. I've installed it once and for all, following your neat instructions and never had to go through the advanced boot method. I'm using "Windows 8 Professional N" and got the legacy drivers from an Asus Notebook running Windows 7 'family' edition.

Thank you all
Blue skies,
Bob