Psp Dosbox

[Cecelia Seiner]

Howeverdosbox is an essential application that I have to startxfce4 to use. Please tell me how to run it in the console. Its entirely commandline based, except the startup, so there must be some way?

P.S- My school uses the ultra-outdated turbo c++ compiler to teach the language. Its got some vendor dependant libraries (conio.h, graphics.h), so its necessary that I use dosbox to run it. If you can't help me with dosbox, then can you please tell me how to run tc.exe in the console. That'll do as well.

An alternative to starting WM/DE would be to use a customized .xinitrc with startx.

all you need to do is have exec dosbox in it instead of exec somewm .

This will start an X session that is exclusively used by/for dosbox .

P.S- Thanks for the quick replies. The Arch community really is awesome. Just like the wiki. This was my first post and now I know where to come after reading the comprehensive wiki you guys have built.

Hello! Got a new Acer Predator Bifrost Intel Arc A770 OC recently and have been having a good experience so far! ... Except for a pesky issue I've found when trying to play some of my retro games that require DOSBox to run. Upon launching DOSBox on its own or games with custom config files and after testing with any and all options modified in searching for the right combination to work...

I have updated to the latest Drivers, Installed and run DDU for all makes of video cards. As I've had NVidia and AMD before the Arc a770 (my prior card was an AMD Radeon RX 6700XT). I've re-installed DirectX using the Jun 2010 Redistributables. I've attempted the different Windows Application Compatibility settings. Tried different ArcControl Game/Compatability settings. I've scoured the interwebz and found no help. I'm at a loss. Can someone here assist, please?

Once DOSBox launches, the windows immediately close with no error, but I do get a couple of entries in the System's application log... Attached along with system info report gathered from the Intel Graphics Command Center. If you need anything else, please let me know.

Well, I did find DOSBox Staging. A newer fork of the DOSBox project: -staging/dosbox-staging. It DOES work with my A770 and my DOS games are working splendidly with it. The issues with the original DOSBox still stand and I'm willing to assist if you all at Intel would like to resolve the issues. But, in the meantime I guess I'll go with DOSBox Staging. Thanks!

This crashing issue with the original version of DOSBox was reported to us and we are at the moment investigating the cause of the problem, please note there is no estimated time for the issue to be fixed since at the moment we are focused on modern games but know this is under our current open issues and has assigned the Bug ID 14020514788, you can use the Bug Id in case you want to check the status of the issue in future threads.

As informed in our previous post the crashing issues related to the original DOSBo software have been investigated by our team so feel free to check back later on with the BUG ID we shared. Since there are no further questions we will be closing this thread, however, feel free to open a new topic if you need further assistance.

We want to let you know that the crashing issues with the original version of DOSBox have been resolved with our latest driver version 31.0.101.5186, please update to the latest version and share your feedback with us.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

PURE automatically assigns the cycles by the year of the game, taking into account the most powerful CPU that was released that year, but it may be that the game does not require the power that was handled that year.

Thank you for respond, I tried MAX-Emulate as many instructions as possible it still has the frigates spinning around. I am playing the 1994 "X-Wing Collectors CD-ROM which I believe it the original 1993 version with the B-Wing expansion

Does it go in my game folder or do I need to create a folder and put it in that along with the unzipped dosbox_pure_libretro.dll file and zip them up together? Because I tried both methods and neither changed anything

This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name.

I've been developing it alongside a source code library I've been writing that is both a learning tool and a functional library to talk directly to various hardware on a DOS PC. DOSBox is one of my testing grounds for this code, alongside VirtualBox and some ancient Pentium-100 hardware sitting around my house.

- Gravis Ultrasound panning register fixes. Mainline DOSBox seems to have a buggy implementation that ends up locking all audio to center no matter what value is written. I fixed that code in this version. DOS programs that rely on stereo sound should actually play in stereo now through DOSBox.

- PS/2 AUX port emulation. This enables DOS programs and OSes to work that don't use INT 33h and communicate directly with the PS/2 mouse connected to the keyboard controllers "AUX" port. This code is wired in so that INT 33h emulation is enabled by default, but shut down the instant the "reset" command is sent to AUX.

- Sound Blaster "Goldplay" support. Back in the early 1990's a tracker library was used in some demos that provided music playback to LPT DAC and various other outputs including Sound Blaster. The problem is the library's Sound Blaster support uses a weird hacked DMA transfer mode that is basically setting the DMA buffer length to 1 byte and having the controller loop over that, then writing the byte from an interrupt handler. Mainline DOSBox tends to render this as a low frequency "rumble", while this fixed version detects that case and plays the audio perfectly. This fix is ideal for some demoscene entries in the 1991-1993 time frame.

- ISA Plug & Play emulation. This is useful for PnP-aware DOS programs or for running Windows 95 within DOSBox. The implementation provides both BIOS and I/O compatible PnP interfaces to the PnP-aware software.

- Serial mouse emulation. You can enter "serial1=serialmouse" into your dosbox.conf to have DOSBox emulate a Microsoft compatible mouse connected to your serial port of choice. Some software made prior to the introduction of PS/2 mice need this. With Windows 1.0, this option is the only way to get a usable mouse cursor within the graphical interface.

- Finer-grained memory sizes. If you want to relive the days when PCs had less than 640KB of RAM or had odd extended memory sizes like 1630KB, you can use the memsizekb= option to specify memory size in KB instead of MB.

- Refresh rate control. You can set a fixed refresh rate that all video modes are locked to. For example if you are capturing content for television, you can force the refresh rate to 59.94 to avoid framerate conversion issues with your video editing software later.

I want to point out though DOSBox 0.74 mainline does NOT emulate a PS/2 mouse. It emulates the BIOS calls, the BIOS callback interrupt, and INT 33h mouse driver functions, but if a program were to actually try and talk directly to hardware to get to the mouse, it wouldn't work. That's why the keyboard controller emulation was improved to emulate the AUX port.

3a8082e126