They really go above and beyond not to describe what this thing is anywhere.
It's a DOS game emulator running DOSBOX for new OSs using legit game copies from the original media.
>Yeah they're like if MAME actually cared about making games playable.
Nah they are like yet another horrendously bloated emulator frontend for mouth breathers who think dragging&dropping .exe on the shortcut is very hard. Retroarch gays, to be precise.
NTA but I am under the assumption that this pack would have dosbox configurations specifically tailored for each game like cycles, hardware settings optimized for each game.
I had the last version, it's good and it does work but DOSbox kind of fricking sucks in 2023. Don't think I can justify downloading so many gigs of data when you can achieve better emulation with other programs now.
I hope you guys enjoy sucking on my teat. This thing is killing my seedbox traffic like no tomorrow. Also letting you know there's a lite version out now on the exo site. It's about 6gig installed. It works by downloading just the game you want to install from the big boy torrent swarm.
I respect that and am the same. What I did was to put the stuff needed for running it on my fast but small SSD and kept the rest on my big ass HDD, then used symlinks to keep it together. Runs pretty smooth tbh.
Frick it I'm just going to download the whole thing minus the media files. I have 4TB drive with 2TB free space I'll just stick it on that and if need be buy another 2tb drive later
>speed is too fast so my external HDD has to queue its writes tanking my DL speed when it gets to many smaller files
The lap of luxury is suffering in its own right.
>there currently isnt a reliable enough emulator to do so
More of an issue of PCem/86box not being suited to per-game configuration like DOSBox is, making it unsuitable for a project like eXoDOS. If it was a matter of reliability, he wouldn't be using DOSBox in the first place since there are still games DOSBox can't run or crashes while running.
Well whatever the terminology. I found the quote from the interview exo did last year:
A 9x pack is my white whale. The primary reason an eXoWin9x pack doesn’t already exist is due to the technical limitations of properly presenting that software within the framework that a project like this demands. To be clear, getting a 9x game running is not necessarily difficult for someone who has the proper tools. The problem is putting together thousands of Win 9x games in a portable manner.
>The first challenge is file size in regards to the operating system itself. For Win3x every single game has its own copy of Windows. This adds about 20mb to the zipped file size of each game. Due to the incredibly picky nature of Win 3x though, this was essentially a necessity. Simply changing the color depth for game 2 would make game 1 stop working. God forbid you update your quicktime install for a new game, as the old game will throw a tantrum and refuse to work anymore. It was also the wild west in terms of how software treated the operating system. Games had no qualms about writing their configuration files directly to the C: or the windows folder. For all of these reasons and more, it was imperative to give each game its own operating system.
>For Win9x, this isn’t possible. A compressed Win98 install takes approximately 200mb. Granted, they can be stripped down smaller by removing all sorts of dependencies, this isn’t feasible to do for every game (thousands of times) nor does it make sense to do this up front and assume it won’t adversely affect games you add later. Currently, we have at least 10,000 identified Win9x games. This would be 2tb in duplicated OS files alone. Not the full pack…. Just Win98 10,000 times. And that is compressed. So for a Win9x pack to be feasible we need parent child images. Something that would allow us to have a master Win98 install, with each game installing to its own child image. This would allow any changes to the OS folders (or the C: at all) to be captured by the childdiff image. The second primary need is dynamic images. Most image based software uses static images that take up the same size on disk as the total size of the image. So, if you create a 1gb drive image, even if it only contains 100mb of files, it will take up a gigabyte on the disk. A dynamic image will grow as the file size grows. This would allow us to report to the OS that there is plenty of free space available without having to make a custom image for every single game that has exactly the amount of space we need for the installed product.
>Ultimately, we need both of these features combined with an emulator that has the horsepower needed to run games released from 1994-2002 (even later honestly). We came close to attempting to use PCem, as it added features very similar to those described above. However shortly after the project went on hiatus for a while and only recently returned. When we are talking about sinking another 10,000+ hours into something, it is key that the software we are relying on doesn’t get pulled out from underneath our feet. It also helps to have a working relationship with the authors, as a project like this is about the biggest stress test you can possibly put an emulator through.
>All of that said, we have an eye on the future and we currently have somewhere between 4 and 6 terabytes of Win9x software images preserved and ready to go. So at the very least, we are trying to prevent the data from disappearing while we await the proper technology to make these games playable again.
So basically pcems troony dev throwing his tantrum and shutting down the project scared them off from using pcem because its dev team is not reliable.
7 months ago
Anonymous
that's pretty encouraging to know they're prepared at least.
why couldn't they use 86Box though? isn't it more updated than PCem?
7 months ago
Anonymous
>why couldn't they use 86Box though? isn't it more updated than PCem?
Lack of parent-child images and lack of dynamic image sizes. It would push the size of a potential exowin9x to more than 10tb at this time.
7 months ago
Anonymous
>lack of dynamic image sizes
I use a dynamic sized HDD image in 86box. It's recognized by DOS as being 2GB's, but it's currently only 200MBs. What is meant by lack of dynamic image sizes?
>God forbid you update your quicktime install for a new game, as the old game will throw a tantrum and refuse to work anymore.
I know games made for Quicktime 1 and 2 won't work under Quicktime 3 or newer, but I would be interested in getting a list of Quicktime 1 using games that won't work under Quicktime 2.
>thoughts?
I got v5 to supplement Total Dos Collection's lack of CDROM games. This guy puts a lot of effort into making the games accessible to moronic zoomers who will never play them.
XP-era games largely work natively on modern Windows without little fuzz. Only shit that can sometimes be troublesome is some of the shitty DRM from back then, but there's usually solutions for that. Worst case, you just run them on a VM.
Does it cost money?
no
Eh, not a huge fan of all the fluff to be honest. I know how to configure a DOS game, thanks. Still a nice archive of games.
They really go above and beyond not to describe what this thing is anywhere.
It's a DOS game emulator running DOSBOX for new OSs using legit game copies from the original media.
Yeah they're like if MAME actually cared about making games playable.
>Yeah they're like if MAME actually cared about making games playable.
Nah they are like yet another horrendously bloated emulator frontend for mouth breathers who think dragging&dropping .exe on the shortcut is very hard. Retroarch gays, to be precise.
NTA but I am under the assumption that this pack would have dosbox configurations specifically tailored for each game like cycles, hardware settings optimized for each game.
I think I read they have specialized shaders for each one too and it has mt32 and roland sound.
You would be correct, and the anon you’re replying to is a dumbass for either intentionally or unintentionally omitting that fact
frick off, moron.
>t. mouth breathers who think dragging&dropping .exe on the shortcut is very hard
Retroarch gays, to be precise.
drive literally not big enough to download it all, sucks
take the vr dospack pill
https://mega.nz/folder/3t8nzSIS#947kyMN6Z80f8HS7q2XlqA
>Not Age of Empires 1
>No Network Q Rally
>Has garbage like Dune 2000
>drivelet
>in 2023
I bought an external 5TB HDD last year off Amazon for a little over a hundred bucks. It's serving me well so far.
Even the version where you pick what to download is too fricking big.
I had the last version, it's good and it does work but DOSbox kind of fricking sucks in 2023. Don't think I can justify downloading so many gigs of data when you can achieve better emulation with other programs now.
What's better? Slow, clunky-ass PCem that needs to boot an entire virtual system and OS and lacks many QoL/enhancement features? MAME or Qemu? lol...
I recall he said that he sticks with dosbox because its well known and you can mount drives to folders.
>161 gigabytes
Haven't tried the new interface thingy for it yet, but doesn't it download what you need as you need it? Thought that's how he pitched it.
Thats the lite version thar isnt out for version 6 yet.
(161gb is only the media files)
The release torrent is over 550GBs I can't even download it as I don't have enough disk space
The light version of 5 was still 50 gigs.
>Download torrent with one game selected
>4gb of metadata in a single zip file out of a total of 6gb being downloaded
Well, we'll see if it works.
>Program can't start because api-ms-win-core-path-l1-1-0.dll is missing from your computer
Frick you and your W10 exclusive garbage.
They have a patch available for Linux systems.
I'm on 7
Bro.
You could at least run the zipped games in dosbox staging or retroarch using dosbox pure, couldn't you?
I'm torrenting the full 685GB file as we speak. Pray for me.
I hope you guys enjoy sucking on my teat. This thing is killing my seedbox traffic like no tomorrow. Also letting you know there's a lite version out now on the exo site. It's about 6gig installed. It works by downloading just the game you want to install from the big boy torrent swarm.
The hoarder in me says to just download the whole thing. I'm done downloading, now I'm just seeding.
I respect that and am the same. What I did was to put the stuff needed for running it on my fast but small SSD and kept the rest on my big ass HDD, then used symlinks to keep it together. Runs pretty smooth tbh.
I have a 5tb external HDD and keep all my roms and old PC games on it. I just run eXoDOS straight off the drive.
98 percent hoo boy
Frick it I'm just going to download the whole thing minus the media files. I have 4TB drive with 2TB free space I'll just stick it on that and if need be buy another 2tb drive later
Nevermind I'll be fricking dead by the time this torrent hits 10% let alone 100
>Come back after 8 hours
>Not even 10mb of 640GB
Yeah... this ain't going to happen.
>speed is too fast so my external HDD has to queue its writes tanking my DL speed when it gets to many smaller files
The lap of luxury is suffering in its own right.
Seeding to eternity (also exodos 5, exoapple, exo3.1 and exoscumm)
These bad boys chew up my bandwidth like no other
we need a project like this for Windows 9x games
They have Exowin, but yeah there's not one for windows 95/98 unless I'm late to the party
exo wants to do that but there currently isnt a reliable enough emulator to do so. he wants to make an exowin95
>there currently isnt a reliable enough emulator to do so
More of an issue of PCem/86box not being suited to per-game configuration like DOSBox is, making it unsuitable for a project like eXoDOS. If it was a matter of reliability, he wouldn't be using DOSBox in the first place since there are still games DOSBox can't run or crashes while running.
plus not to mention youd have to bundle it with a copy of windows 95/98 preset and that would probably cause even more issues than the dos games
Well whatever the terminology. I found the quote from the interview exo did last year:
A 9x pack is my white whale. The primary reason an eXoWin9x pack doesn’t already exist is due to the technical limitations of properly presenting that software within the framework that a project like this demands. To be clear, getting a 9x game running is not necessarily difficult for someone who has the proper tools. The problem is putting together thousands of Win 9x games in a portable manner.
>The first challenge is file size in regards to the operating system itself. For Win3x every single game has its own copy of Windows. This adds about 20mb to the zipped file size of each game. Due to the incredibly picky nature of Win 3x though, this was essentially a necessity. Simply changing the color depth for game 2 would make game 1 stop working. God forbid you update your quicktime install for a new game, as the old game will throw a tantrum and refuse to work anymore. It was also the wild west in terms of how software treated the operating system. Games had no qualms about writing their configuration files directly to the C: or the windows folder. For all of these reasons and more, it was imperative to give each game its own operating system.
>For Win9x, this isn’t possible. A compressed Win98 install takes approximately 200mb. Granted, they can be stripped down smaller by removing all sorts of dependencies, this isn’t feasible to do for every game (thousands of times) nor does it make sense to do this up front and assume it won’t adversely affect games you add later. Currently, we have at least 10,000 identified Win9x games. This would be 2tb in duplicated OS files alone. Not the full pack…. Just Win98 10,000 times. And that is compressed. So for a Win9x pack to be feasible we need parent child images. Something that would allow us to have a master Win98 install, with each game installing to its own child image. This would allow any changes to the OS folders (or the C: at all) to be captured by the childdiff image. The second primary need is dynamic images. Most image based software uses static images that take up the same size on disk as the total size of the image. So, if you create a 1gb drive image, even if it only contains 100mb of files, it will take up a gigabyte on the disk. A dynamic image will grow as the file size grows. This would allow us to report to the OS that there is plenty of free space available without having to make a custom image for every single game that has exactly the amount of space we need for the installed product.
>Ultimately, we need both of these features combined with an emulator that has the horsepower needed to run games released from 1994-2002 (even later honestly). We came close to attempting to use PCem, as it added features very similar to those described above. However shortly after the project went on hiatus for a while and only recently returned. When we are talking about sinking another 10,000+ hours into something, it is key that the software we are relying on doesn’t get pulled out from underneath our feet. It also helps to have a working relationship with the authors, as a project like this is about the biggest stress test you can possibly put an emulator through.
>All of that said, we have an eye on the future and we currently have somewhere between 4 and 6 terabytes of Win9x software images preserved and ready to go. So at the very least, we are trying to prevent the data from disappearing while we await the proper technology to make these games playable again.
So basically pcems troony dev throwing his tantrum and shutting down the project scared them off from using pcem because its dev team is not reliable.
that's pretty encouraging to know they're prepared at least.
why couldn't they use 86Box though? isn't it more updated than PCem?
>why couldn't they use 86Box though? isn't it more updated than PCem?
Lack of parent-child images and lack of dynamic image sizes. It would push the size of a potential exowin9x to more than 10tb at this time.
>lack of dynamic image sizes
I use a dynamic sized HDD image in 86box. It's recognized by DOS as being 2GB's, but it's currently only 200MBs. What is meant by lack of dynamic image sizes?
>God forbid you update your quicktime install for a new game, as the old game will throw a tantrum and refuse to work anymore.
I know games made for Quicktime 1 and 2 won't work under Quicktime 3 or newer, but I would be interested in getting a list of Quicktime 1 using games that won't work under Quicktime 2.
by the by, if you want a backup easy DL of most of the exodos games without using torrents, The Eye eu has a backup hosted of V5
>thoughts?
I got v5 to supplement Total Dos Collection's lack of CDROM games. This guy puts a lot of effort into making the games accessible to moronic zoomers who will never play them.
I wonder if it would ever be feasible to have an ExoWinXP collection. is there even any emulator for Windows XP era PCs?
XP-era games largely work natively on modern Windows without little fuzz. Only shit that can sometimes be troublesome is some of the shitty DRM from back then, but there's usually solutions for that. Worst case, you just run them on a VM.
you know that you can select what you download from the torrent right? at worse, it's a pre-configured DOS game downloader on demand
The lite version is out now which will download on demand for you so you dont even need to be celective on the torrent.