xokia Posted February 12 Posted February 12 3.19 hosed my setup. Don't know why its putting the word file in the path. Also would be nice if we had an option to roll back instead of having to ask for a old release. Can I get 3.18 please? The specified path is invalid. : '\\HOME-SERVER\pool5\games\LaunchBox\file:\Z:\Arcade\SNK Neo Geo Pocket Color\roms'. App: LaunchBox Version: 13.19 Theme: Default Type: System.IO.IOException Site: WIN32_FILE_ATTRIBUTE_DATA GetAttributeData(System.String, Boolean) Source: System.Private.CoreLib at System.IO.FileSystem.GetAttributeData(String fullPath, Boolean returnErrorOnNotFound) at System.IO.File.GetAttributes(String path) at Unbroken.LaunchBox.Windows.Desktop.ViewModels.RomImportLocationParseViewModel.<>c__DisplayClass10_0.CompareAutowireTag(Object) at Unbroken.LaunchBox.Windows.Desktop.ViewModels.RomImportLocationParseViewModel.<>c__DisplayClass10_0.AssetReadableConnection() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CancelPrincipalIdentifier(Object) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CalcInvalidPage() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) Recent Log: 8:18:25 PM Exception Quote
xokia Posted February 12 Author Posted February 12 I can confirm this is an issue with 3.19 luckily I still had the 3.18 laying on my server. Re-installed and all works again Quote
AstroBob Posted February 12 Posted February 12 Hi there, Thanks for the report here. Right off the bat, that file path definitely seems a bit off. Can you confirm. - Go to Tools > Manage > Platforms, and then into your Neo Geo Pocket Color platform. - Under the Folders tab, what is the path listed there for Game Can you also take a single pocket color game and edit it's metadata, go to Launching and then provide an example of what the ROM File path looks like? Finally, can you confirm: - Does this error occur for other platforms, or just Neo Geo Pocket Color - Can you confirm where these affected games are stored? It looks like it's some sort of network or external drive. Please let us know and we'll try to get you sorted Quote
xokia Posted February 12 Author Posted February 12 (edited) 6 hours ago, AstroBob said: Hi there, Thanks for the report here. Right off the bat, that file path definitely seems a bit off. Can you confirm. - Go to Tools > Manage > Platforms, and then into your Neo Geo Pocket Color platform. - Under the Folders tab, what is the path listed there for Game Can you also take a single pocket color game and edit it's metadata, go to Launching and then provide an example of what the ROM File path looks like? Finally, can you confirm: - Does this error occur for other platforms, or just Neo Geo Pocket Color - Can you confirm where these affected games are stored? It looks like it's some sort of network or external drive. Please let us know and we'll try to get you sorted I already switched back to 3.18. This happens when I try to add roms. I have a mapped drive called games. Z drive. When I choose the importer is starts off in \\Home-server\balh\.blah instead of Z:\ even when I installed in Z:\ Then when I browse to Z:\path_to_roms it will insert the file path it has along with file:\ in the name prepended to the actual path Edited February 12 by xokia Quote
faeran Posted February 12 Posted February 12 26 minutes ago, xokia said: I already switched back to 3.18. This happens when I try to add roms. I have a mapped drive called games. Z drive. When I choose the importer is starts off in \\Home-server\balh\.blah instead of Z:\ even when I installed in Z:\ Then when I browse to Z:\path_to_roms it will insert the file path it has along with file:\ in the name prepended to the actual path A very specific scenario that we are unable to reproduce on our end. Every attempt at importing either a UNC or mapped network drive is successful. If you can zip up your Data folder and send it to me in a PM that may help track down what's going on in your build. Quote
xokia Posted February 12 Author Posted February 12 Sure I can upgrade again later this afternoon. Quote
xokia Posted February 13 Author Posted February 13 (edited) Just sent you both working 3.18 and broken 3.19 so you can diff Only thing I can think of that was done different is 3.18 install file is sitting on the network drive 3.19 install file is sitting on the local drive. Both were pointed to the Launchbox directory on the network drive to install into. Edited February 13 by xokia Quote
xokia Posted February 13 Author Posted February 13 Doing all that switching and rolling back now broke my MAME set importation. Hoping this can be resolved. Object reference not set to an instance of an object. App: LaunchBox Version: 13.18 Theme: Default Type: System.NullReferenceException Site: Void PrintInvalidIterator() Source: LaunchBox at Unbroken.LaunchBox.Windows.Desktop.ViewModels.MameFullSetWizardRomLocationViewModel.PrintInvalidIterator() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ChangeAwareVisitor(Object ) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.PopSessionProcessor() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() Recent Log: 8:23:08 PM Exception Quote
C-Beats Posted February 13 Posted February 13 Try going to Tools > Download > Force Update Games Database (last option) and letting that run before doing any importing or scraping Quote
xokia Posted Friday at 12:16 AM Author Posted Friday at 12:16 AM (edited) 10 hours ago, C-Beats said: Try going to Tools > Download > Force Update Games Database (last option) and letting that run before doing any importing or scraping Tried that did not fix anything Edited Friday at 12:18 AM by xokia Quote
xokia Posted Friday at 04:34 AM Author Posted Friday at 04:34 AM (edited) upgrading to 3.19 fix the MAME set importer but import Rom is still broke. I Can not import ANY roms. It inserts that "file:" into my path and everything breaks. Also themes dont work under BigBox Edited Friday at 08:54 AM by xokia Quote
xokia Posted Friday at 11:37 PM Author Posted Friday at 11:37 PM (edited) Any progress? 3.18 is less broke then 3.19. Themes work fine under 3.18. Maybe its not correct to say 3.18 is broke. 3.18 worked 100% until upgrading to 3.19. After upgrading then reverting back to 3.18 MAME import is broke. Let me know if there is anything I can do to assist in debug. Edited Saturday at 12:13 AM by xokia Quote
xokia Posted Monday at 09:46 AM Author Posted Monday at 09:46 AM (edited) Here is what it looks like when I try and import a rom with 3.19. Same exact import with 3.18 Edited Monday at 09:51 AM by xokia Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.