Jump to content
LaunchBox Community Forums

Recommended Posts

Posted
Thanks guys. Unfortunately I've tried both and they're both working fine for me, sigh. Anything you can give me at this point would be helpful; screenshots, videos, etc. Or even just a very detailed description of exactly what is happening and what you see. Also, if you go into your Windows Event Viewer and go to the Application log, it should give you some info on the crash at the top of the log. That might be useful as well. Beyond that I'm baffled. Oh, what version of Windows are you guys running? @DonkeyKongsVet @scree
Posted
I will work on a video, I will walk through the beta install as well, maybe something in there I didn't pick up on that might have also been key and I will take a look at what Windows has to say on it and see if that has any answers I run Windows 10 Home...32 bit
Posted
I bet it is, I just launched it off from my One Drive (a backup source for anything that happens) with my 64 Bit, Windows 10, Home system, no issues with the beta Execute it with the 32 bit system right off one drive, does the same thing as if I run it off my D drive
Posted
Can you two do me a favor? Create a separate copy of LB real fast and update that to the latest beta. If it loads and crashes that's fine, what I am more curious about is changing the VLC line in the XML. Load up your LaunchBox.xml with Notepad++ or something equivalent and search for "VLC" without the quotations. Replace VLC with Windows Media Player, save the XML and try opening LB again. We want to see if it's a VLC issue, neither of us have 32bit machines handy.
Posted
Wonderful, I was about to state I can not find anything to do with VLC in my xml file, I even installed to my C drive and did a search for VLC and nothing returned, but I have a VLC folder
Posted
DonkeyKongsVet said Wonderful, I was about to state I can not find anything to do with VLC in my xml file, I even installed to my C drive and did a search for VLC and nothing returned, but I have a VLC folder
You searched the LaunchBox.xml and it found nothing related to VLC? huh... either way Jason is apparently super on top of it today. Let us know if the new beta fixed you.
Posted
I will let you know how the new beta works, I am getting back to another 5.8 version installed elsewheres to try it. Yeah, nothing with VLC in Launchbox.xml file that I could find, I didn't check my One Drive copy
Posted
New beta is up. The issue was ultimately that I was mistakenly loading 64-bit VLC native DLLs for both 64-bit and 32-bit environments. Let's hope this fixes things. :)
Posted
It failed on me still, got the same exact issue, I am taking a look around because when I mentioned that there was nothing about VLC in my xml file on my system, I figured that was a flag, the one drive has reference to VLC in the xml file, but I get the same problem still even if I launch it from one drive. I am taking a spin around some logs on the system to see if something gets my attention that could be playing a part in this. I checked the XML file on the C and D drives, the D drive has Beta 10, C drive has Beta 9 both have no indication about VLC in the xml file, only my one drive copy does, but that still quits if I launch from the 32 bit but not the 64
Posted
The VLC setting is added upon saving the LaunchBox.xml file. It makes sense if it's crashing that it never gets saved and thus the VLC setting never gets added. I'll have to put a 32-bit virtual machine together so I can test this I guess.
Guest
This topic is now closed to further replies.
×
×
  • Create New...