Pink discos are worth half a heat . <| sep |> I legitimately thought you were in your twenties and honestly am still not convinced otherwise <| sep |> Kendisinden kaanlar tarafndan oluutulan grubu ele geirip , Bana gvenin ne olur demek en hafifi tabirle terbiyesizliktir nk . nsanlar dier gruptan atp baka yere toplayarak bize maraba olarak davranmaya almtr . <| sep |> Thank you so much again ! You are amazing ! Bless you ! !<| sep |>' Member when people just called comments like that references ? <| sep |> Seriously man . Wouldn ' t the front page be interesting again without all that TD crap all over it every single day ? I hope they all take their toys and go play someplace else . <| sep |> Russia did not meddle . <| sep |> Windows 3 . 1 can start apps from the dosbox console . It ' s how i use it , i mount a game dir as d the windows 3 . 1 dir as c and just run cwindowswin . bat dgame . bat from the autoexec section of the conf file or similar . I ' m also not aware of any limitation of resolution of win 3 . 1 running in dosbox except ofc , the native drivers . But you are indeed right about gog being able to benefit for selling win 3 . 1 games , because they ' re unwilling to license windows 3 . 1 from microsoft . BUT if they go the windows only route that it seems this emulator uses , i ' m not going to use anything but the datafiles . I like the security and platform agnostic compatibility that dosbox gives . I ' d actually be much more interested in a windows 95 reimplementation that runs on dosbox . because the usability and filesystems feature barrier between mounting a image and mounting a directory is vast deduplication and write redirection data size using unionfsfuse for example , not to mention how FAT 32 running on windows 95 is a fragile filesystem that corrupts images at the drop of a hat not so bad with a copy on write cache from unionfsfuse , but still annoying . It was suggested to me that if the qcow 2 filesystem was implemented as a image format supported by dosbox , i could use its feature to redirect writes to a smaller file to take care of that ' large copyonwrite ' problem with a another smaller copyonwrite . Unfortunately the format is highly coupled to qemu and the only patch implementing it for dosbox is very naive and requires copying the whole backing data to memory , which is obviously a problem when it ' s 5 gb . There is a standalone library , libqcow , but it doesn ' t implement this part of the format or even writes . So currently for using win 95 games on dosbox i do this terrible dance of copying the windows image to ramdisk from the conf file , so not portable , and the game image to disk cache from a premount unionfs write redirect script . The actual game data is stored in a read only compressed squashfs with other console ROMs that don ' t need rw so don ' t have the redirect script . This isn ' t much of a problem for normal DOS games that just want to write a single mb at most , but for windows 95 games they have to write to a large disk image thus the reason i wanted qcow 2 support in dosbox . Even external mounting support would not help because win 95 running in dosbox requires image support in dosbox . It actually works even for win 95 7 gb games black dhalia but it ' s a bit annoying not being as efficient as possible . If anyone reading this is wondering how it ' s possible to use a 7 gb image file on dosbox , there is a separate patch for that . I really have no idea why it ' s not merged except stubbornness from upstream . No big prob , i applied it to my ppa .