Now it works and have a NMS8245 at 60Hz, with 256KB RAM, and FMPAC in the (before) free 3-1 subslot.
Nice. The XML files are a great place to create custom machines. Take a look at the boosted configurations for inspiration. you may want to set your number of drives to two for instance. That won't cost you any memory.
Now it works and have a NMS8245 at 60Hz, with 256KB RAM, and FMPAC in the (before) free 3-1 subslot.
Nice. The XML files are a great place to create custom machines. Take a look at the boosted configurations for inspiration. you may want to set your number of drives to two for instance. That won't cost you any memory.
Indeed, for working can be nice to be able to mount 2 folders at the same time due to limitation of 720KB. Have to test if they can coexists with a HDD.
Anyway it would be great to have an option in openMSX to set the default VDP frequency: A set_freq rather than toggle_freq. In MSXgl I setup target MSX according to project options but I have no easy way to setup frequency on this emulator (Emulicious for example have this kind of option).
This doesn't really make sense. The software can change the frequency any time... as Wouter explained, the BIOS sets the initial frequency and running software can change it at any time.
On MSX1 machines (with TMS VDP) it depends on the VDP used. We emulate that VDP and such VDP generates a video signal at a certain frequency...
What's the problem of using an NTSC (default) machine?
Maybe aoineko refers to breaking out toggle_frequency into a set_frequency and get_frequency. Within the limitations of what that can do of course (V99x8 only, and software can change it at any time).
On real hardware the frequency is not save in the CMOS of the Real Time Clock (https://www.msx.org/wiki/Real_Time_Clock_Programming#Block_2).
I'm not sure why the news I submit to MSX.org are not being published anymore, but 2 years ago I published a new version of the MSX2 BIOS with many enhancements, and it fixes this issue. The vertical frequency is now also saved to the RTC by the SET SCREEN command.
https://twitter.com/SnatcherAlpha/status/1343352359532040193
Cannot make the IDE to work from hardware description XML. Adding the IDE extension to any slot or sub-slot in XML does not boot from the HDD, shows IDE "stuff" but then boots to BASIC. If once powered I add the extension, IDE alone or attached to a slotexpander, and reset, it boots from the same HDD that refuses to boot before.
Cannot make the IDE to work from hardware description XML ...
I assume you copy/pasted the content of the ide.xml tag inside your new machine description file (the part inside the "primary/secondary" tags, and then changed the slot=any" attributes to specific values (0-3)). Right?
A bit further in the ide.xml there's the "filename" tag with value "hd.dsk". By default filenames in machine/extension descriptions are specific for that machine/extension. This allows to create multiple machines/extensions that each have their own separate harddisk image.
You could edit this "filename" and use an absolute path to the "hd.dsk" file of your ide extension. But then be very careful to not accidentally use this extension in your new machine. Then both will potentially modify the same image and this can easily result in a corrupt image.
A safer solution might be to copy your "ide" hd.dsk image over the corresponding file of your new machine.
BTW: the real-world analogy of this scenario would be: you buy a new hardisk, built it into your MSX machine. And then you're surprised it doesn't contain the same files as your old external harddisk ;-)
You could edit this "filename" and use an absolute path to the "hd.dsk" file of your ide extension.
Well it was path related. Because the 1st time I used the ide extension the HDD was created into /persistent/ide/untitled1/ I modified that HDD, but that's the one associated indeed with the IDE external extension. If added to the machine, it is created at /persistent/machine_name/untitled1/. Modifying that HDD works.
Thanks.