Ian Spencer wrote: > if I select for ex. atomhd.hdf as an atom drive in drive 2 Simcoupe > forgets my selection every time I exit the program
Thanks - I've reproduced this, and it was something I broke only yesterday when making some last-minute tweaks (always fatal). Dan Door� wrote: > I have just noticed something similar with some options like > the 'auto boot on startup screen' which if you set them, exit > and then go back in they stay but if you exit and then launch > a .DSK file that fires up the EXE the option is lost. I can't reproduce this, using with the Win32 EXE installer version (as I'm guessing you're using that one for the file associations?). The check-boxes on the Drives tab should always reflect the last state set by the user, with nothing forcibly changed by SimCoupe itself. I've checked the 'autoboot' option in the code and it's only updated during the OK button processing for the Drives tab. If a disk image is passed on the command-line the emulator does a one-time autoboot of the disk regardless of the autoboot option setting, as it's highly likely you'd want to boot it. As it starts a new instance of the emulator there's no risk of losing anything in memory by attempting it. This one-time boot doesn't make any changes to the autoboot option, so if it wasn't set it still won't be for any further disks inserted (at the startup screen) during the same session. Does any of that differ to what you're seeing, or how you expected it to work? Edwin Blink wrote: > This just sounds like a work directory problem. > When you start the exe the config file is created in the > startup dir where simcoupe is. It did sound a bit like that, but the Win32 version always accesses the SimCoupe.cfg file in the same directory as SimCoupe.exe, regardless of the current working directory. While on that subject, is there any demand for sharing a single SimCoupe installation between multiple users? I've thought about adding another option to use the current user's My Documents directory for SimCoupe.cfg, allowing each user to have separate settings (like most of the other SimCoupe ports already do in $HOME). Other issues that have cropped up in the latest beta (thanks to Edwin and Frode for these): - when automagically booting (using either the internal SAMDOS2 image or the user's own DOS), it fails to run the AUTO* on the original disk after booting DOS, returning to BASIC with an OK message instead (fixed). - when scanlines are enabled in the Win32 version, the black alternate lines sometimes accumulate garbage, particularly if the debugger or built-in GUI are opened (hopefully fixed). - sound was disabled on Solaris due to an endian mismatch between the expected and obtained sound formats (hopefully fixed by relaxing the check). I've already worked through most of the above, so there should be an updated version available sometime tomorrow... Si
