Re: Windows 95 On Psp Using Dosbox Download And Set

0 views

Skip to first unread message

Message has been deleted

Jalisa Landgren

unread,

Jul 16, 2024, 9:39:09 AM7/16/24

to beaupresaccoc

I have successfully installed Windows 98 in dosbox-x. However I am unable to actually mount any cd's as windows98 doesn't seem to recognize the mounted CD drive. I am able to mount them in Dosbox-x it self, which is how I was able to install windows98 in the first place. But when windows98 boots up and i got to My Computer it only shows C:(mounted hdd) and A:(floopy). Im pretty new to this and tried to look around on the wiki if it's even possible or if i was going about it the wrong way. In the autoexec part of the config I added "MOUNT D G:\ -t cdrom -ide 2s" with "G" being a virtual drive on my host machine. I assumed it would mount dosbox-x's "D" drive as my hosts "G" virtual drive and I would be able to use that in Windows98. And I apologize if this isn't the correct place for it.

Here's my assumption (beware: sounds definitely unprofessional and may even be completely wrong): unlike 'network cards' in virtual machines the Dosbox/WinPcap-solution simply acts as a 'tunnel' for the network card on the guest, a cable based NE2000 in this case. So in effect using a wireless card as interface card in Dosbox means trying to connect a cable based LAN card to a Wireless Network. Which obviously doesn't work since the NE2000 doesn't 'talk' WLAN.

windows 95 on psp using dosbox download and set

Download https://miimms.com/2yWfwo

New to the board but have been using NI GPIB bus technologies for five years in my line of work. I am currently underway in rewriting some DOS based applications into Windows so that we can support later operating systems but we still have a lot of legacy code written. I've been exploring the possibility of using DosBox to give some of these applications new life under Windows 7 and later operating systems. One particular application is a work horse and very versatile app written and maintained by one of our application's engineers.

Emulation works fine with the GPIB-ENET devices though I have found that sometimes I am forced to use the internal cards because some NI drivers have bugs when it comes to emulating the GPIB card over the network. In addition to that, we've also come across timing issues using them that aren't present using local cards.

GaryNeal, I'm running into almost the exact same issue with a DOS GPIB program that we have. Did you have to any special modifications/settings to DosBox in order to use your application? Our program is using an old version of Microsoft Advanced Basic, but it does not seem to be communicating via GPIB.

To launch Windows, type cd windows to change to the Windows directory, then type win to start Windows. At this point Windows should load successfully, but without sound. We need to install sound and video drivers to get the most out of the Windows 3.1 experience.

To run on Windows 95 or NT4 without Active Desktop requires a modification to DOSBox so that it doesn't store the dosbox.conf in the user profile, see my thread here where I am wiriting guides on compiling DOSBox: DOSBox Compilation Guides
For NT3.51 a further change is to modify the DOSBox configure to use WSOCK instead of Winsock2.
For NT3.50 a further change it to modify SDL to disable fullscreen and copy the joystick file from 3.51 to 3.50.

....you lost me a bit though. I visited that thread, and dosbox.conf it says "Need to look into setting dosbox.cfg or dosbox.ini in dosbox code although dosbox still reads "dosbox.conf" as "dosbox.con" in DOS anyway" - then links to a Github which doesn't mention dosbox.conf anywhere so I don't quite know what exactly I have to do to modify this to run on my Windows 98SE system...

Which release do I want there? The options which may pertain to me are: dosbox351x32.exe, dosboxx32.exe, (NT one isn't for me as I'm running 98SE), or dosbox95x32.exe (which I assume will work on Win98SE)? I browsed the documentation folder and didn't see what the difference is between versions. Struck out in googling all those mentioned on the same page too (sorry if I'm asking stupid questions...I'm trying to be proactive and find the answer myself but I struck out...)

If you want to use my builds then just use the ones from the Google Drive link. The only diff between those and official DOSBox is they are using the latest SVN as from when they were compiled whereas 0.74-3 is the same as 0.74 game compatibility wise

I should have some new builds up using the latest SVN fairly soon assuming RL doesn't get in the way again. There is one posted at the end of my thread but make sure you use overlay or opengl with that one.

Downsides:
Slight increase in size
Used only for 98 and ME which would further bloat the guide or just use the unecessary file alignment switch for all Windows Operating Systems which wouldn't make any sense.
Latest VS that supports this is VS 2008 which is the last version to support 9x using the current method in my guide. Although I plan to look into 9x using VS2010+ using the method in my previous posts.

I don't know exactly which versions of MS-DOS will work, but I suppose 7 should be fine too. I've read that you can cheat Windows into accepting a different version by using set ver 6.0, but I can't confirm this myself since if you use 6.22 you'll never run into this problem.

2. Make a hard disk image
You can do this using the bximage program that comes with Bochs. HAL9000's Megabuild contains a built in command for creating these from within DOSBox. (Would be awesome if that could be merged with the main branch.)

All you really need to remember when using bximage is the cylinder count, since everything else is standardized and shouldn't be changed. In my example I'm making a 400 MB image which has 812 cylinders. Only flat images are supported (as of this time of editing). Sparse images will not be recognized. However, it's possible to still compress flat files using your host OS's filesystem; in Windows XP, this is the default behavior (hence the blue filename).

Note: you may need to replace c.img with the name you gave your image file, and replace 812 with the cylinder count you used when creating the file using bximage. It should say Drive number 2 mounted as c.img. You might notice that we're not giving it a drive letter: basically, every drive needs to have a filesystem, which is a sort of file index, before it can be used properly. Without a filesystem (like FAT32, NTFS, HFS+, etc.) a filesystem is just empty, unorganized space that the operating system can recognize but can't really do anything with, so until we fix this problem we can't mount it under C or any other drive letter yet. Modifying filesystems on a drive is called partitioning.

At this point, DOSBox should say "Drive C is mounted as c.img". If something is wrong, start this step over. Don't attempt to access the C drive from DOSBox's own DOS shell or you might make it unreadable for pure DOS. Now boot into MS-DOS by using the same command as last time:

4. Copy over setup files and start Windows 95 installation
At this point you should have your Windows 95 disc ready. The version should not matter all that much; I'm using a Dutch OEM version myself, the same one I got with my first Pentium computer about 17 years ago.

The easiest way to do this (to my knowledge, anyway) is to mount the c.img file in your operating system. qbix mentioned that mount -o loop dos622.img /mnt should do it on Linux. I'm on Mac OS X myself and can mount it by double clicking on the image file in the Finder. On Windows, I'm not entirely sure if this is possible, but a program like Isobuster should work too. Dominus recommends using DiskExplorer which is free. Make sure you close DOSBox before you move the files.

It's possible to get internet working using HAL9000's NE2000 passthrough patch, but it requires compiling your own version or using his Megabuild. I'll update this guide later when I get that working.

On Mac OS X, make sure you don't set the screen bit depth to anything over 8-bit (256 colors). 16-bit and 32-bit are broken and causes visual glitches. I've also found that it's MUCH faster in full-screen mode when using the opengl output system.

Only flat images are supported (as of this time of editing). Sparse images will not be recognized. However, it's possible to still compress flat files using your host OS's filesystem; in Windows XP, this is the default behavior (hence the blue filename).

I have also tried imgmount 3, imgmount 2 c x:\c.img (where x: is the dosbox directory where c.img is located mounted in dosbox), imgmount 2 c c:\dosbox\c.img, and every other logical combination I can think of.

Hi
I run windows 95B under dosbox 0.74
With machine=svga_s3 the display of icons is completely messed up for 256 colors, 16 bits and 32 bits colors.
I tried somes other s3 drivers but I didn't found something working properly
It is working for someone with svga_s3 ?

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

I use Ubuntu 22.04.2 LTS, I recently installed and configured Turbo C on dosbox, i attend online courses and use Turbo C to practice.Is there a way that i can use super+tab or alt+tab to change between full-screened dos window and chrome?Are there any other shortcuts?

I'm trying to play an old game (Betrayal in Antara) and I found an old post where it was said that the game runs well under win 3.x in dosbox so I have installed Windows 3.1 in DosBox but whenever i start it up i get the following error messages -