On Thu, Sep 28, 2000 at 10:03:29AM +0100, Simon Owen wrote: > Dave Whitmore wrote: > > would it be possible to alter a DSK image, to another filetype with a > > different extension that could be recognised by Windows (or another > > GUI O/S) to launch Sim Coupe, and in turn boot itself.
You can use whatever filetypes you like - have one for autoboot and one for not-autoboot if you really want (after all, what's in a name? It's just an entry in the registry) - but I'm not sure I see the point in the not-autoboot one so one might as well just use the DSK filetype as an autoboot disk. > Yes - you can set up an associated application to be run when you > double-click on .DSK files. The SimCoupe command-line can include the > options to insert the disk and boot from it. You can also set up additional > entries on the context (right-click) menu for that type, so that make it > just inserts the disk without booting, etc. > The only trouble is that the current versions of SimCoupe fail because > Windows makes the directory containing the .DSK file the current directory, > and SimCoupe will fail to find the SAM ROMs. You could probably do it with > an intermediate batch file for now, but that's messier. I'm not familiar with associating filetypes with commands, but if you had the batch file then you could have the batch file supply all the '-disk1 foo' and '-autoboot' flags which simcoupe needs. Associating *.DSK with that batch file might then be easier than associating it with "simcoupe -autoboot -disk1 foo". Or I suppose it might not make any difference. If you wanted to eliminate the batch file you could add another flag argument to simcoupe which allows you to specify which directory the ROM files are in. imc
