Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: upgrading fb32 (Read 2750 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

upgrading fb32

In order to preserve the metadb, what I did was copy portable installation "C:\foobar2000.portable.32bit\" to "C:\foobar2000.portable.64bit\", then do an in-place installation of foobar x64 into "C:\foobar2000.portable.64bit\".

After the above is done, foobar x64 is working good.
I notice no "profile" folder is created.
The "user-components-x64" is created under "C:\foobar2000.portable.64bit\" instead of "C:\foobar2000.portable.64bit\profile\".

Will this pose a problem in the future?

For future proofing, do you recommend I do a fresh/clean install so that the "profile" folder is in place, and find another way to migrate metadb?

.
 

Re: upgrading fb32

Reply #1 –
There is absolutely no need for a clean start, upgrades are fully supported.
I see no reason to fear the "profile" folder being missing, except perhaps around foobar2000 v3.0 release... Though even then if it causes issues it will likely be because of a bug.
But if you want, you can create the profile folder yourself and manually move all profile data there.

Re: upgrading fb32

Reply #2 –
Quote from: Case on
But if you want, you can create the profile folder yourself and manually move all profile data there.

Just to be sure ... after I move them, foobar will automatically look for them in the profile folder?

Screenshot from my test portable installation .. the folders in green, and config/databases/files in red?



.

Re: upgrading fb32

Reply #3 –
Yes. And you can always create a backup before any operation so it's easy to return to where you were.

Re: upgrading fb32

Reply #5 –
It was about a hypothetical future release a decade from now.

Re: upgrading fb32

Reply #6 –
What does this error mean?

Re: upgrading fb32

Reply #7 –
It means you have a been naughty and removed the 'runtime' directory with all the required Universal C Runtime dll files.

Re: upgrading fb32

Reply #8 –
Quote from: Case on
It means you have a been naughty and removed the 'runtime' directory with all the required Universal C Runtime dll files.

My bad! Yes that was the problem. I put it back ... all good now. Thank you!

I got some 32bit rubbish hanging around the upgraded fb64 folder ... and am painstakingly removing one by one ... to check which ones are still in use.

Thankfully I am doing on a "test migration" copy.

Re: upgrading fb32

Reply #9 –
Quote from: boxerfan88 on
I got some 32bit rubbish hanging around the upgraded fb64 folder ... and am painstakingly removing one by one ... to check which ones are still in use.
https://learn.microsoft.com/en-us/sysinternals/downloads/sigcheck

SendTo this batch file:
Code: [Select]
cmd.exe /k c:\sigcheck\sigcheck64.exe -a %1
pause

Re: upgrading fb32

Reply #10 –
Okay, I did the production migration, so far so good. Documenting what I did for reference.

First, I created the "profile" folder.

Second, I moved these folder/files into the "profile" folder.


Third, I parked the "folder/files that I think is no longer needed" into a staging folder.
These are the folder/files that I parked for deletion later.


Finally, I restarted the "migrated" fb64 for the first time. It threw an error saying that some foobar components are messed up and suggested to reinstall (I forgot to take a screenshot).

Next, I reinstall fb64 portable on top of itself.  Then, I restarted fb64, all is good!!

Some small niggles to fix (eg. re-pointing foo_uie_webview data folder and template path to the new path).

I am now in a good place for foobar 3.0 :)

Re: upgrading fb32

Reply #11 –
Quote from: boxerfan88 on
...
I am now in a good place for foobar 3.0 :)

We have a tagline in Polish that "there is no smoke without a fire".
What is going on with this "3.0"? This is the second time in last two weeks. Last time I was stalled "well, this is something very historical". Definitely it is NOT.
ANY info, please ;)

Re: upgrading fb32

Reply #12 –
Quote from: papavlos on
What is going on with this "3.0"?...

ANY info, please ;)
It is a reference to the far future.  No 3.0 is even postulated yet, let alone on the drawing board.

We have the same phrase in English, but in this case the smoke is hypothetical, and so is the fire.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: upgrading fb32

Reply #13 –
The recent change from 2.2 previews to 2.24 to indicate the year was a big enough thing already. 2.25 is obviously coming next and I'd expect regular previews all next year before a final release towards the end of it.

2.24 might get some point releases if serious bugs are found but given the length of the preview cycles now, that should be happening less often.

Re: upgrading fb32

Reply #14 –
It's because @boxerfan88 has successfully migrated from 32-bit to 64-bit and then expressed his readiness to fb2k 3.0.
So my attention: What? Is it going to be 64-bit only? What then with our precious 32-bit only plugins, like "foo_upnp"?

Quote from: fooball on
It is a reference to the far future.  No 3.0 is even postulated yet, let alone on the drawing board.
We have the same phrase in English, but in this case the smoke is hypothetical, and so is the fire.
Quote from: marc2k3 on
The recent change from 2.2 previews to 2.24 to indicate the year was a big enough thing already. 2.25 is obviously coming next and I'd expect regular previews all next year before a final release towards the end of it.
2.24 might get some point releases if serious bugs are found but given the length of the preview cycles now, that should be happening less often.

Thanks for clarifying! So, the business as usual... No emergency alerts (yet).   O:)