The following is straight from -Max Lingua- out of one of the 1.7.0 readme documents. If I have enough time when I'm done researching and typing this I will set something up. ![]() Normally, I would make a new thread and start from scratch. If I had the first post in this thread, I would edit in your bug list, along with any others that pop up in the future, so the Devs in charge would always have a clear list for all versions with only one place to look. Unless you need a newer version for a specific game I still recommend version 1.4.1 for the ps2 regardless of internal hard drive or usb configuration. Any intermixed saves from the correct version will load fine. Saves you make with 1.7.0 are not backwards compatible with an older version however, for example, if you try a 1.7.0 save in a 1.4.1 setup it will produce an error on the save screen for those specific saves on their respective lines. I was able to save again and the new save is still there after reboot. To verify for you, after reading your post, I reinstalled and booted 1.7.0 on the ps2 hard drive and, the saves made from that version still load without issue. I personally played Zak Mckracken 100% (from start to completion) using a hard drive on 1.7.0 during initial testing and still have the 8 saves I made in that version. To get your saves working from hard drive, read my post on the following link: You say that savegame function IS working from usb,īUT in your first sentence you say that it does NOT work at all from usb. Enjoy!ĭen1982 wrote:No, scummvm does not working from usbmass anyway.Ĥ. For me that is still the best version until a new one is released which fixes the savegame bug. It will create a ScummVM folder with an icon.sys file, scummvm.icn file, and yes even create its own ScummVM.ini file. That version requires a memory card to run proper but atleast it will automatically save your settings when you run it if you have a memory card in the first slot. As far as I can recall it worked 100% right out of the zip with no modifications and you can setup your configuration right from the frontend launcher. That is the setup I prefer myself as everything in that version seems to work flawlessly (with the exception of reloading a savegame before quitting to ensure it actually saves). If you are having slower speed problems or any other setup/config problems I would highly recommend "ScummVM 1.4.1 official release with the 14,033kb scummvm-N.elf". Without looking at my own setup I believe the only differences with running it on usb would be to change these in the ini file. Game7Cmd= -conf "nf" -conf "dosboxKQ7_nf" -noconsole -c exitĪnd you're done! Running the "Legacy" version of the game should now run the games in DOSBOX.Congrats on finally getting it started, glad I could help! Game7Path=\2016_KingsQuestCollection\kq7\dosbox Game6Cmd= -conf "nf" -conf "dosboxKQ6_nf" -noconsole -c exit Game6Path=\2016_KingsQuestCollection\kq6\dosbox Game5Cmd= -conf "nf" -conf "dosboxKQ5_nf" -noconsole -c exit Game5Path=\2016_KingsQuestCollection\kq5\dosbox Game4Cmd= -conf "nf" -conf "dosboxKQ4_nf" -noconsole -c exit Game4Path=\2016_KingsQuestCollection\kq4\dosbox Game3Cmd= -conf "nf" -conf "dosboxKQ3_nf" -noconsole -c exit Game3Path=\2016_KingsQuestCollection\kq3\dosbox Game2Cmd= -conf "nf" -conf "dosboxKQ2_nf" -noconsole -c exit ![]() Game2Path=\2016_KingsQuestCollection\kq2\dosbox Game1Cmd= -conf "nf" -conf "dosboxKQ1_nf" -noconsole -c exit Game1Path=\2016_KingsQuestCollection\kq1\dosbox Start King's Quest Collection normally (non-legacy) and everything should just work. If you copied the directory correctly and edited the configuration file, you're finished. #Game6Cmd= -no-console -f -p.\kq6\ kq6-cd Game6Cmd= -no-console -f -p.\kq6\ kq6-cd-win #Game5Cmd= -no-console -f -p.\kq5\ kq5-cd Game5Cmd= -no-console -f -p.\kq5\ kq5-cd-win Game5Name=KQ5: Absence Makes the Heart Go Yonder #Game1Cmd= -no-console -f -p.\kq1\ kq1-coco3
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |