Romcenter

It seems wine 3.15 64bit and dotnet40 gives the best result so far.
yes, tested before, unfortunately the result is the same as with dotnet46.

this combination works for a few? people (even with the same base), so there must be something missing, i guess? if you have some ideas left or a new rc ...

hi there,

i changed all (say one) logger to off and started rc, but it made no difference.

still a flood of uriformatexception boxes until it closes on its own.

sorry for not giving you no more actual hints...

i was interrested to see how rc behaves under a fresh dotnet46 prefix.

actually the same uriformatexception error comes up, but the terminal ouput was very different this time.

perhaps it is useful somehow, here you go:


wine RomCenter.exe
0012:fixme:wer:WerSetFlags (2) stub!
0012:fixme:heap ...

so rc4.0 actually works for you now?

i gave it a new try, now on wine 3.15 64bit and dotnet40.

this error message shows up on top of the rc logo:


uriformatexception: invalid uri: hostname could not be parsed.
romcenter will now close.


it closes automatically after a few sec.

still no error ...

it could be my x64 prefix after all, but to be fair, none of the tools (32/64 bit) i use gave me problems whatsoever.

sure, i'd be interrested in a test version, but please take your time.

this i have done already, forgot to tell you, sorry.

so dotnet40 is really the only precondition?

i have tried with different locations that are valid within wine, but no log file is being generated?

bizarre.

sorry for the late reply.

here is the specs:

wine 3.4 64bit
dotnet40 64bit

unpacked romcenter (which contains a nlog.config file) to home folder. ran romcneter, logo appears for 1 sec.

no new log file has been created during that process. the nlog file has not changed after all.

hi,

i registered only today so to ask for romcenter 4.0's prerequisits, in order to get it running under wine 3.3.

what i have tried so far, is dotnet40 and dotnet45, where as the latter not even shows the initial logo while loading.

the terminal output has no concrete error showing up, so i am a ...