Romcenter 4 support discussion. Please do not post roms requests or illegal links, posts will be deleted. After discussion in this forum, please report any new bugs here.
I have manually placed (not installed, i'm using the portable RC version) RC 4.1.1 in its current folder. I tried executing rc.exe with certain parameters from RCDBManager. Before that, i had to change the current dir to romcenter's dir because rc.exe complained it could not find Rc_nlog.config. So after that, the result was the following:
RomCenter.Global.BaseLog/Error : Unable to determine the DbProviderFactory type for connection of type 'FirebirdSql.Data.FirebirdClient.FbConnection'. Make sure that the ADO.NET provider is installed or registered in the application config.
Unhandled Exception: System.NotSupportedException: Unable to determine the DbProviderFactory type for connection of type 'FirebirdSql.Data.FirebirdClient.FbConnection'. Make sure that the ADO.NET provider is installed or registered in the application config.
at System.Data.Entity.Infrastructure.Net40DefaultDbProviderFactoryResolver.<>c__DisplayClass5_0.<GetProviderFactory>b__0(Type t)
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at System.Data.Entity.Infrastructure.Net40DefaultDbProviderFactoryResolver.GetProviderFactory(DbConnection connection, IEnumerable`1 dataRows)
at System.Data.Entity.Infrastructure.Net40DefaultDbProviderFactoryResolver.ResolveProviderFactory(DbConnection connection)
at System.Data.Entity.Utilities.DbConnectionExtensions.GetProviderFactory(DbConnection connection)
at System.Data.Entity.Core.Common.DbProviderServices.GetProviderFactory(DbConnection connection)
at System.Data.Entity.Utilities.DbConnectionExtensions.GetProviderInvariantName(DbConnection connection)
at System.Data.Entity.Internal.InternalConnection.get_ProviderName()
at System.Data.Entity.Internal.LazyInternalConnection.get_ProviderName()
at System.Data.Entity.Internal.LazyInternalContext.get_ProviderName()
at System.Data.Entity.Internal.DefaultModelCacheKeyFactory.Create(DbContext context)
at System.Data.Entity.Internal.LazyInternalContext.InitializeContext()
at System.Data.Entity.Internal.InternalContext.Initialize()
at System.Data.Entity.Internal.InternalContext.GetEntitySetAndBaseTypeForType(Type entityType)
at System.Data.Entity.Internal.Linq.InternalSet`1.Initialize()
at System.Data.Entity.Internal.Linq.InternalSet`1.GetEnumerator()
at System.Data.Entity.Infrastructure.DbQuery`1.System.Collections.Generic.IEnumerable<TResult>.GetEnumerator()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at RomCenter.DataAccess.Firebird.EF5.Ef.GetCurrentConfig(IRdtConfig config)
at RomCenter.DataAccess.Firebird.EF5.Ef..ctor(String fileName, IProgressTracking progressPack, IPauseAndCancellationToken pauseAndCancellationToken, Boolean validatedb)
at RomCenter.DataAccess.Dal..ctor(IConfiguration config)
at CommandLine.romcenter.CreateRomcenterEnv()
at CommandLine.Program.RunCreateAndReturnExitCode(CreateOptions createOptions)
at CommandLine.Program.<>c.<Main>b__11_1(CreateOptions options)
at CommandLine.ParserResultExtensions.WithParsed[T](ParserResult`1 result, Action`1 action)
at CommandLine.Program.Main(String[] args)
I can't reproduce the problem.
I have created a batch in another folder and did a cd romcenter\ as first command, and it works.
Then I remove this command, create a shortcut of the batch and set 'start in' to romcenter\ in shortcut properties, and it's still working.
OK, i think i have found the cause of the problem. I compared the contents of rc.exe.config and RomCenter.exe.config, and i noticed the following part missing from rc.exe.config:
Nice work!
I don't know why it works on my station, probably the db full installation provides some default settings...
Anyway, I added it for next version.
RomCenter wrote: Sat Apr 10, 2021 7:32 amAnyway, I added it for next version.
Great. From what you said, the next RC version will use a .NET version greater than 4.0, so it won't be XP compatible. For those few that may still be using XP, it might be nice to release a 4.1.2 version on the site (same files, just include this minor change in the zip) stating that this will be the last XP-compatible version.
Just an idea.
And a question. I'm guessing the "fix" parameter performs a fix of the database with some default fixing parameters, right? Are they retrieved from somewhere (RC's config perhaps)? Is there a way (or a plan) for the user to define them in the command-line version?
Yes, the xp version will remain. I have upgraded the win10 branch to be ready for .net 4.7 and up, and I reports changes to the xp branch.
Now I'm fixing issues reported in xp branch, and I will merge them in win10.
The goal is to maintain xp with functionnal issues, and keep win10 up to date with components and new technologies.
About config in command line version, the goal is to allow loading config from a text file. For now, it uses default settings.
RomCenter wrote: Sun Apr 11, 2021 8:38 amThe goal is to maintain xp with functionnal issues, and keep win10 up to date with components and new technologies.
OK, i have managed to make almost everything work. create, add rom path and fix. The only command i have issues with, is update. It just says Success and does not change the database. Of course it works fine from within RC GUI, only command-line behaves like that.
I have used the following two TOSEC dat packs:
TOSEC - DAT Pack - Complete (2974) (TOSEC-v2019-05-10)
TOSEC - DAT Pack - Complete (3036) (TOSEC-v2020-07-29)
From the first one, i have created a DB using Amstrad CPC - Games - [DSK] (TOSEC-v2015-05-07_CM).dat and then i tried to update it using Amstrad CPC - Games - [DSK] (TOSEC-v2020-07-12_CM).dat from the other dat pack.
Don't know why, but it took about 1-2 minutes to download and the file was corrupted. I tried it twice in two different days. It seems that the download is not completed normally. The two files i downloaded had the same contents, but one of them had more data than the other.
EDIT: OK, third time was a charm. Now it unpacks fine.
Hmmm... Web provider issues???