To remind you, we already have this kind of view, somehow... Yeah, i know it's slow when you have 400+ entries in D-Fend Reloaded - and the pictures are not scaleable, but it's definitly there. 😀

I see LaunchBox as a niche product that is NOT competing with D-Fend reloaded, but me thinks this "look" SHOULD be implemented into D-Fend Reloaded. The Option "View"->"Screenshots" is simply not nailed down enough to specific Filenames in D-Fend Reloaded. It get's messed up with BoxShots and …

The game has several files in which the actual path of the game is definded. These are: All.rdf Boot.rdf User.rdf Open these files with a text editor and change them from (e.g.): c:\wonderla\Two.rsc 362496 c:\wonderla\Three.rsc 362496 c:\wonderla\Four.rsc 362496 c:\wonderla\Five.rsc 362496 c:\ …

Tried all of the above and i must say that ONLY ADDiCT's -windowgui switch hint works. Don't know how all these patches and fixes from Jk Hub are supposed to work, but they only corrupt the Jk.exe. So -windowgui works best.

I got it working, too. You need to select "Soundblaster Pro" from the "Setup" and "15 FPS" at "300 Hz" Refresh cycles to have the cut-scenes lip-synced. All other selected Soundcards just output plain nothing.

I tried Interstate '82 (german version) today on Vista-SP1 and found out that it's not working out-of-the-box. It crashes when it should load the selected mission. Fix: Rename i82stub.exe to e.g.: i82.exe and it works like a charm! Hope that helps! 😁

I can confirm that the first release of Tie Fighter (Disks) runs very slow. You need to set cpu=dynamic and cycles=max . Then (depending on your PC's horsepower) it runs absolutely fluid . The differences between the fist release (Disks) and the CD-ROM Collectors Edition? Well, i quote mobygames …

I have the same output on my machine, here and no overlay configuration or RAM amount stops Crusader from showing the above. I tried it with DOSbox 0.72 under Vista with nVidia 182.55 drivers installed. Haven't found out what the problem is. Guess it's a Graphics-Card problem? Has onybody here found …

I used your installer and it worked fine ONLY because of the Paths set in the Resource.cfg file: videoDrv = VGA.DRV soundDrv = GENMIDI.DRV audioDrv = DACBLAST.DRV joyDrv = NO audioIRQ = 7 cmd = GKCD mouseDrv = none memoryDrv = none minmemory = 2M CD = NO smartdrv = YES mode = protected audio=.\;.\ …

The first post mentioned the issue - Flickering in Blood and loss of colors (green/grey) with DosBox 0.71 & 0.72. If you don't have any issues with your Dosbox version, you'll probably won't need the newest version. But since nobody actually encountered this issue, nobody needs a new version, right? …

Hi guys, i said i'd let you know when the issue has been identified or fixed. So far i don't know what caused this issue on blood, but even the dosbox authors said it worked fine. And guess what? It's as i said... Wait for the Daum-Cafe Version and everything works fine. Get the new version at …

So nobody else has this effect? Mhhhh :depressed: I guess i'll never find out until nVidia releases a non-beta driver. As i said, i tried the original dosbox.conf and the graphics are still messed up, so the settings are not responsible for this effect. I also tried all different "output" settings, …

Ok, dunno what happened, but in 0.71 it first works fine but after a few seconds of walking around, the graphics start to mess up (everything turns into red & green pixels). In 0.72 there's only the flickering in the lower half of the screen - the graphics don't mess up. Perhaps it's the 163.44 beta …

No, it does not. I would have not written anything here, if that wasn't true. As i said, it works in 0.71 and flickers in 0.72, using the same dosbox.conf Maybe some tech-info helps?: ASUS P5NE-SLI Core2Duo 43000 @3.0GhZ Geforce 8600 w. Forceware 163.44 beta Vista Ultimate w. all Patches Maybe i'll …

Hi there, i just installed DosBox 0.72 and tried Blood with it. What a mess! Polygons start flickering and one can see through walls. The lighting also shines through walls. 😳 I tested it with 0.71 - no problems. So it must be 0.72-related. Could someone please look into this? 😉