sundogak

I use Firefox and works fine showing all menu items. Not sure why DuckDuckGo would impact it.

So you are not seeing a moderation option in your DB login?

Are these checked in LB?

Likely it is issue with the natural keyboard emulation within the driver for this system. Autoboot requires it to work properly. Fiddling with the command within MAME directly you can see that it doesn't matter what is after the first letter in quotes after issuing command as it won't type anything after (doesn't matter the character). Looking at the driver code at GitHub shows comments that keyboard emulation isn't complete. As this is prelim with many of the carts shown as not working and keyboard emulation needs to work fully for autoboot, there likely isn't much to do. I tried some crazy spacing /combos and it would type additional characters but not in way could control to type "load" (much less the 1 in quotes). The command line should type out whatever you put in after quote, so definitely some parsing issue with the driver. So I think you are out of luck on this one until more work done of the driver. One note for future is that anything requiring quotes needs three quotes on each side of character so would be """1""" (see below).

Below is my log on working version. Only real difference is your bank 0 dip switches and I have gamepad switch set. But nothing in your dip switch setting would prevent running as A3 and A7 are set on for normal operation. I do have note on my batch file for the Enhanced version that it doesn't work with OpenGL, but don't see you set that switch. The fact it is stopping at the view port generation makes me think some sort of video driver conflict but otherwise I don't see anything obviously wrong as it is loading and finding all the needed parts. So not much help.....🤔 2024-11-13 19:45:18.367 INFO [36872] [reset_logfile@348] Version v2.11.3 2024-11-13 19:45:18.367 INFO [36872] [reset_logfile@352] Command line: hypseus.exe dle11 vldp -framefile ..\vldp\dle11\dle11.txt -blank_searches -min_seek_delay 1000 -gamepad -seek_frames_per_ms 20 -homedir G:\Emulators\Hypseus -fastboot -bank 0 11011001 -bank 1 00100111 -nocrc -noissues -sound_buffer 2048 -fullscreen -useoverlaysb 1 2024-11-13 19:45:18.367 INFO [36872] [reset_logfile@353] CPU : AuthenticAMD || Mem : 16320 megs 2024-11-13 19:45:18.367 INFO [36872] [reset_logfile@354] OS : Windows 10/11 || Video : NVIDIA GeForce GTX 1080 2024-11-13 19:45:18.368 INFO [36872] [reset_logfile@355] RGB2YUV Function: C 2024-11-13 19:45:18.368 INFO [36872] [reset_logfile@361] Line Blending Function: C 2024-11-13 19:45:18.368 INFO [36872] [reset_logfile@368] Audio Mixing Function: C 2024-11-13 19:45:18.579 INFO [36872] [SDL_input_init@505] Loading Game Controller system with HAPTIC support 2024-11-13 19:45:18.892 INFO [36872] [SDL_input_init@513] Found G:\Emulators\Hypseus/gamecontrollerdb.txt 2024-11-13 19:45:18.930 INFO [36872] [SDL_input_init@516] Loaded 525 Game Controller mappings 2024-11-13 19:45:19.090 INFO [36872] [SDL_gamepad_init@608] Gamepad #0: T16000M connected 2024-11-13 19:45:19.145 INFO [36872] [SDL_gamepad_init@608] Gamepad #1: vJoy Device connected 2024-11-13 19:45:19.145 INFO [36872] [SDL_gamepad_init@617] Gamepad #1: Haptic Rumble support 2024-11-13 19:45:19.277 INFO [36872] [game::load_compressed_rom@941] Loading compressed ROM image dle11u1l.bin ... 8192 bytes read. 2024-11-13 19:45:19.277 INFO [36872] [game::load_compressed_rom@941] Loading compressed ROM image dle11u2l.bin ... 8192 bytes read. 2024-11-13 19:45:19.278 INFO [36872] [game::load_compressed_rom@941] Loading compressed ROM image dle11u3l.bin ... 8192 bytes read. 2024-11-13 19:45:19.278 INFO [36872] [game::load_compressed_rom@941] Loading compressed ROM image dle11u4l.bin ... 8192 bytes read. 2024-11-13 19:45:22.185 INFO [36872] [video::notify_stats@2220] Viewport Stats:|w:640x480|v:640x480|o:320x240[s]|l:2560x1080|o 2024-11-13 19:45:23.185 INFO [36872] [ldp_vldp::read_frame_conversions@1030] Framefile parse succeeded. Video/Audio directory is: G:/Emulators/Hypseus/framefile/../vldp/dle11/./ 2024-11-13 19:45:23.512 INFO [36872] [video::notify_stats@2220] Viewport Stats:|w:1440x1080|v:1440x1080|o:720x540[s]|l:2560x1080|o 2024-11-13 19:45:34.548 INFO [36872] [ldp::pre_search@178] ignoring seek because we're already on that frame

EXO doesn't need LB to run, it just makes it easier. See #5 below. You don't launch any of the batch files for EXO directly from DosBox. The batch files are designed to call the appropriate emulator in the Emulators folder (see #8) then spawn the program. The version of LB in the EXO package is pretty old. You should make sure you can even run LB in VM by just downloading most current free version and seeing if will run. LB does have various dependencies that on a Windows computer it will install automatically. In VM, not sure if that happens and without them LB won't run. I have run a Mac VM in Windows but not other way around. Don't set compatibility back to old versions. Also don't run LB in admin mode. Have no idea why OneDrive would be going and cloud storage, never seen that with Exo but not using lite version. If you want to run a program outside of LB that will be easiest to troubleshoot. Assuming you installed exo in paths it wants to see then you can go to the following directory (!dos), click on Install.bat and then after completed you can launch from the game batch file. No LB needed: The Install puts the files here: The exo auto installer can sometimes be wonky but on a new install it should be okay. Key is that EXO expects things in certain folders as batch files are used. Below is typical install folder setup for EXO. As long as the paths within the EXO folder are as it expects then the batch files will run. The key folders are the ExoDOS, emulators, and dosbox folders. Now whether this will all run inside a VM (or the EXO updater/downloader), I am somewhat doubtful but if you can run DosBox then potential. The key though is making sure your folders are correct and base install works. Running LB in the VM (assuming can get running) won't be very speedy. Space may also become an issue as you add media to LB. The full exodos package is about 800 GIGs. ExoDOS has a Discord so may ask there as pretty unique use case (and not really a LB issue if cannot run the base EXO package).

If you have auto import on (see snap below) then my suggestion is to delete the PS3 platform and re-add as there were changes in how PS3 and Vita games were imported a few versions back. LB now uses the emulator itself to tell what games are to be imported assuming auto import is on. If auto import is not on or you do not use it then I would delete only the game entry that is having issues and re-add manually. Assuming you have auto import on then do as follows: Create backup of your data just in case. Right click on platform and select delete. Most of the time, if you wait a few minutes, LB will reimport the platform and games. Note it takes the game names directly from RPCS3 so can get some titles you may have to fix to match to LB DB. If for some reason auto import doesn't re-add the platform then can add by going to Tools, Manage, Platforms, and selecting add For PS3 and Vita you need to make sure your roms folder for that platform is pointing to an empty directory (not where you eboot.bin files are) as LB uses the emulator entries. If point to your PS3 folder with files it will duplicate and add things again in addition to auto import. In my case below my "Games\Sony Playstation 3" folder has nothing in it (I use separate drive/folder) but auto import did its thing and added whatever was in RPCS3 outside LB. For the folks at beginning of thread who had the issue with the decryption error that is coming directly from RPCS3 and not LB. Likely that means LB is pointing to wrong eboot file that wasn't decrypted so double check via RPCS3 directly the path to the file that is working. This is especially the case if you had a PS3 setup prior to the auto import feature being added and then turned auto import on as it can create some odd errors with PS3 prior setups. Thus, the re-adding platform and letting LB auto import do its stuff may fix issues there. LB has nothing to do with decryption otherwise.

As long as USB 3.0 or higher and speaking about a spinning HDD at 7,200 or 5,400 rpm then your internal and external HDD will be (roughly) the same speed. The HDD becomes the choke point for speed, not the USB 3.0 or SATA III interface. If go to SSD then which interface you use for full throughput matters. For USB connection just make sure using a good USB 3.0 cable that is certified as such.

Atom cassettes are not supported by MAME at this point. You can look at the HASH directory and look at the atom.xml and says "<software name="GAME NAME" supported="no">" in entries in the list. Also can use this site: http://adb.arcadeitalia.net/dettaglio_mess.php?software_name=backgamm&software_list=atom_cass&search_id=2 Also this thread is useful for cass usage (MAME standalone not RA):

@BigBearPoetThis is an issue across all emulation for CD-i as the digital video cartridge hardware has not been emulated. Not likely to be resolved anytime soon as specs for DVC are sparse. List of CD-i programs that need DVC to run.

Glad figured issue. But also in the "Ugh nothing ever simple" ..........the use of %romfilename% will break RA's "Content Directory" overrides if using them. As RA doesn't seem to be "smart" enough to parse the MAME.ini it used to launch the program (odd). Will have to do a bit more playing around but if use Content level overrides you have to stick with the %romfile% variable. You can see how RA sees it if go to Information and once running will revert to Core Overrides.

@coliver33 My guess at this point is that spacing in path is causing issues when LB parses command. Particularly because it is double space and likely some escaping issue and LB missing a "space" so from RA view doesn't know what to launch. Although I know you said it works outside of LB, we are now dealing with 4 levels of stuff to deal with 1) LB command, RA, MAME, and MAME Software List all of which have their oddities and make difficult to troubleshoot where things are going wrong. With SL, simple is best on paths. At any rate could try two things to check above with particular focus on that "(Merged)" path being double space. Under your MAME SL level directory make a simple directory name (say software) and copy the ..software\archimedes\3dtanks.zip, point LB to it and see if that works. If so then that double space is issue and likely good to know for future as may cause other glitches. Likely "better" solution. LB added new variables within last several months (which haven't bothered to try as don't mess with RA if works!). The %romfilename% strips out path and extension which for MAME SL is actually the preferred way even within MAME standalone as MAME only needs to know the game name not anything else (as takes from XML/INI data). You also get advantage of MAME using the XML data. If do it this way then SHOULD take care of any spacing issues as you are not sending anything from LB to RA other than file name (no extension or path). As you said RA works fine out side of LB then in theory the double space aspect should not come into play from LB view. "aa310 -bios 200 -flop \"%romfilename%\"" In example above with zip you used it would then look like this to RA incoming: aa310 -bios 200 -flop 3dtanks You keep the RA setup as before as far as check boxes as still need quotes stripped other than what we explicitly put in. I tried this and works as well on my setup with %romfilename% and launches 3dtanks. Note: edited slightly to delete the "-flop1" to "flop" as if using this method the XML will parse to correct drive.

@coliver33A couple additional things. It looks like they deprecated that Mame.opt option of "boot from CLI" so wouldn't worry about that line (used to need that so not sure what they did there). One thing I noticed is you are pointing LB to Retroarch two folder layers deep. Was that intended to have Retroarch inside another RA folder? LB needs to point to same setup EXE as what you are using outside of LB. In your MAME RA INI above you show RA path one level down (as normal) so you should be pointing to that exe. Likely that is part of problem as the MAME system files in RA don't match.

2) allows rom paths outside RA System directory, specifically to a normal MAME install path.

1) Yes, it works for me. RA with MAME standard core: 2) Using the base MAME core you don't need to move anything around from standard install of MAME arcade and MAME software lists. Bios files remain as for normal MAME. So you don't need to move the bios into System folder for RA. 3) MAME.ini for RA in system directory doesn't looks consistent. Should just point to standard MAME arcade ROMs folder and standard MAME software list set. If have CHDs separate then those as well. Example: 4) Then on your MAME options file for RA should have this which for SL the red boxes are key: Using above you can keep a normal MAME set and also use for RA. Because of the an issue/coding glitch you have to have updated copies of HASH XMLs and Samples within the MAME RA system folder (won't work pointing to MAME install) even though the intent of the RA "MAME_PATHS_ENABLE" was to be able to use all MAME normal paths. But at least for ROM MAME paths they can reside outside RA folder structure.