VOGONS

Common searches


D-Fend Reloaded (DOSBox frontend)

Topic actions

Reply 2120 of 2280, by sst

User metadata
Rank Member
Rank
Member

@Alexander
7-Zip 15.12 stable released version (2015-11-19) for Windows.
http://7-zip.org/

Are you able to update "7za.dll" Inside "D-Fend Reloaded", to "7za.dll v15.12 (2015-11-19)" stable released version soon ?

Until you include the "7za.dll v15.12 (2015-11-19)" stable released" update, ... did i use x64 or x86 "7za.dll" Inside your D-Fend Reloaded software ?

Reply 2121 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

Hi sst,
yes, I can update the 7za.dll library with the next version of DFR. But at the moment I haven't got any plans for a new version of DFR. So updating 7za.dll could happen in the more distant future.

Reply 2122 of 2280, by sst

User metadata
Rank Member
Rank
Member

@Alexander

You have not responded this question.

Until you include the "7za.dll v15.12 (2015-11-19)" stable released" update, ... did i use x64 or x86 "7za.dll" Inside your D-Fend Reloaded software ?

Then, ... in clear.
Did for the moment, i can place manually myself, the "7za.dll v15.12" x86 or the x64 version inside your software? Or it need programmation from you, to be able to use this "7za.dll v.15.12".
Also what will be needed "7za.dll x64 v15.12" or "7za.dll x86 v15.12"?

Reply 2124 of 2280, by kashicommodore

User metadata
Rank Newbie
Rank
Newbie

Bug report.

Just been having an issue with DFR crashing on me when I try to run my games. And a google search reveals this issue has been raised before.. namely the MIDI settings crashing everytime a .conf file is generated.

For reference, the response to the last person to report this, back in 2012 - Re: D-Fend Reloaded (DOSBox frontend)

I am having the same issue as the previous reporter. If I try to select a MIDI device (obtain the list of devices) via the profile editor, or if I specify one manually in the editor and then run that profile, DFR crashes. It certainly has something to do with .conf file generation, because if I set DFR to always make .conf files for profiles, the crash occurs when saving the profile (if a device was specified manually). If I don't make .conf files, the crash occurs on game start. [The crash always occurs when trying to get a list of devices in any case.]

I use CoolSoft VirtualMIDI but I have the same effect on a PC with BASSMIDI instead. I haven't sadly been able to try it on a PC with no additional 3rd party MIDI software (yet).

At the time, Alexander seemed to believe it was due to the default template having no disks/volume records defined in it (indeed, he lists it as fixed in the release notes for 1.3.0) but I can assure you the default template disks are there and defined. In fact, they are not altered from the out of box settings. 😀

Luckily, using CoolSoft as my default MIDI device in Windows, then simply using 'intelligent/win32' allows me to use my MIDI software just fine.

Is there any additional bug info or reports I could give you to aid you in fixing this issue, Alexander? Not that it's important in my specific case but i thought I might be able to aid reproduction of the bug.

[My system: DFR 1.4.4 in 'progdir' mode, not installed on C drive, Windows 7 x64 SP1, 16GB RAM.]

Apologies for poor english.

Reply 2125 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

I do not have CoolSoft VirtualMIDI and cannot reproduce your problem. For me the MIDI device selection is working. As a workaround you can add these lines in the "Custom settings" box of the DOSBox page in the profile editor:

[midi]
midiconfig=...

Here you can enter any custom MIDI configuration (refer to the DOSBox manual for the syntax). These lines are passed to DOSBox without any further processing by DFR.

Reply 2126 of 2280, by viritys

User metadata
Rank Newbie
Rank
Newbie

Hi,

fun little bug that took me far too long to figure out: dfr is unable to understand dos path<=>longer path. This in itself could be called a feature, but it's a bug when using other emulators;
a) I add an emulator to, say, C:\Emulator\Sony\Sony Playstation (1994)\ePSXe 1925\ePSXe.exe
b) I add a number of games, everything's fine, games are under Playstation
c) I close DFR. When I open it the next time,
d) Emulator path changes in settings to dos path D:\Emulator\Sony\SONYPL~1\EPSXE1~3\ePSXe.exe but the original windows path is found from each individual game
e) All my previously added Playstation games are recognized as Windows games as DFR gets confused between the two versions of paths

So I guess this can be fixed by either making dfr understand both presentations of paths, choosing not to rename the path in "other emulators" or changing the paths in game profiles as well.

Not worth its own post but now that I'm already writing, might as well mention this one as well:
There's something going on with the row length when adding games with wizard and forced word wrapping: Say you add a new game and add few rows worth of notes. The number of characters that can fit a row depends on the width of characters, apparently. Anyway, save profile and the moment you go to edit mode and open the program information the first time, it will break each individual row to two pieces;
So
1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456

are both maximum length rows in wiz. Open the program editor and they become

1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'9'1'3'5'7'
9'1'3'5'7'
12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
0123456

I suppose the easiest fix would be to remove the forced word wrap.

Reply 2127 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

Hi viritys,

I've tried to reproduce the problem but if I follow your steps the path name does not get shortened on my system. The path name of the custom emulator just stays (as expected) in long format.

The automatic word wrap in the notes fields are intended. So the user does not need to wrap texts in longer paragraphs or to scroll while reading. If you resize the main window or the notes section inside the main window the word wraps in your example strings will disappear. Also the tree in the profile editor window can be resized to make the right section larger and therefore to allow longer lines.

Reply 2128 of 2280, by viritys

User metadata
Rank Newbie
Rank
Newbie

For the 1st one: interesting, it does that to me constantly. Any idea what my conflicting setting could possibly be?
For the 2nd: I'm not sure what you're suggesting - the line breaks are sticky for me after I do it the way I described. Maybe some pictures could explain it:

1) Add game with wizard, add notes:
UyGpvBe.png
2) all is good:
bgfjAK6.png
3) but after visiting notes in editor:
SpcmS9K.png

and those row breaks are stickies that no resizing will fix

Reply 2129 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

Looks like the run time library edit boxes are adding line wraps when wraping a long line into multiple lines. When storing the text back I cannot distinguish between the original and the added line wraps.

Reply 2131 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

I didn't know DOSBox-X yet. If it's using the same configuration file format as DOSBox, you can just add a DOSBox-X installation as an extra DOSBox installation for being used in DFR via the setup dialog. If it's working in a completely different way, you can still use it by adding it as a custom emulator in the setup dialog. At the moment I'm not planning to add any specific DOSBox-X support to DFR.

Reply 2132 of 2280, by Estel Randir

User metadata
Rank Newbie
Rank
Newbie

Lately I have been playing around with DFR vs the front end I normally use. Something curious I have noticed. I installed MUNT & tried to use it with several games that do support MT-32. They sounded aweful. I tried it in DFR & the sound was as it should be - sounded great. I then took all the lines under [midi] in the DFR game profile & copied them to [midi] in the profile the other front end used. I then bypassed the front end by creating a dosbox shortcut directly to the profile. It still sounded like crap.

What is DFR doing that is so much better than the other front end with regards to MT-32?

Reply 2133 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

DFR is not doing anything special. All communication with DOSBox is done via the conf file. So identical conf files should lead to identical results. Maybe not only the settings in the [midi] section have influence on the sound quality in the game you are using. The available CPU cycles for example may also have an impact on the sound quality.

Reply 2134 of 2280, by ikrananka1

User metadata
Rank Newbie
Rank
Newbie

With my installation of Windows I have moved my user profile (and user directories) to my D: drive instead of the C: drive which is where Windows is installed. I have been trying to get DFR to setup and use its data directories under D:\Users\<username>\D-Fend Reloaded but am not managing to get it to cooperate.

When the program is installed, it by default creates its user directory structure under C:\Users\<username>\D-Fend Reloaded. I then go into the program options and change the directories to point to the D: drive instead of the C: drive. If I then quit the program, delete the DFR folders on the C: drive and then restart DFR, it prompts with the first-use dialog box and, after I select OK to continue, it simply recreates all of the data directories again on the C: drive.

How can I get DFR to use the D: drive for all data instead of C: ?

BTW - this is installed in operational (non-portable) mode.

Reply 2135 of 2280, by Alexander

User metadata
Rank Oldbie
Rank
Oldbie

Changing the base folder for relative path names does not change the location of the configuration folder. It only means relative path names like ".\VirtualHD\SomeGame" in the profile editor are interpreted as relative to some other base folder. If you want to use some other directory than "%UserProfile%\D-Fend Reloaded" as data folder for DFR, you have to install DFR in program folder mode or in portable mode. The easiest way to get DFR to some other folder or drive is using the "Transfer programs..." function from the Extras menu. This function is intended to transfer games from one installation (for example the default user directory using installation) to another one (for example a portable installation on an USB stick). By checking the "Create portable D-Fend Reloaded installation in destination folder" you can also copy the program files (by keeping all user settings but setting up the destination installation to be a portable installation). So start your old default installation (using the data on drive C:), select the "Transfer programs..." function and create a complete copy of DFR and all games on drive D:. When starting the new DFR installation on D: it will just use the data on D: and you can remove the old installation and the "%UserProfile%\D-Fend Reloaded" folder.

Reply 2136 of 2280, by ikrananka1

User metadata
Rank Newbie
Rank
Newbie
Alexander wrote:

Changing the base folder for relative path names does not change the location of the configuration folder. It only means relative path names like ".\VirtualHD\SomeGame" in the profile editor are interpreted as relative to some other base folder. If you want to use some other directory than "%UserProfile%\D-Fend Reloaded" as data folder for DFR, you have to install DFR in program folder mode or in portable mode. The easiest way to get DFR to some other folder or drive is using the "Transfer programs..." function from the Extras menu. This function is intended to transfer games from one installation (for example the default user directory using installation) to another one (for example a portable installation on an USB stick). By checking the "Create portable D-Fend Reloaded installation in destination folder" you can also copy the program files (by keeping all user settings but setting up the destination installation to be a portable installation). So start your old default installation (using the data on drive C:), select the "Transfer programs..." function and create a complete copy of DFR and all games on drive D:. When starting the new DFR installation on D: it will just use the data on D: and you can remove the old installation and the "%UserProfile%\D-Fend Reloaded" folder.

Thanks Alexander. Am I correct that reinstalling in portable mode would be the same as installing using the defaults and then following your "Transfer programs..." instructions above? I have uninstalled DFR and so want to know if simply reinstalling in portable mode would achieve the same thing as you are suggesting.

Are there any downsides, limitations or other issues associated with running games from a portable mode install?