You can get a command overview with
# flashtool ?
To set the maximum wait time, use
# flashtool maxwait <n> persist
For persisting a setting, the flash must be in unprotected mode (hold right mouse button at power-up)
The CacheCDFS archive contains only a program that goes to SYS:Prefs/ and a handler that goes to L:. To the best of my knowledge, a handler doesn't need the execute flag. Setting the "execute" protection bit on the prefs program in the command line would look like this:
# protect sys:prefs/cachecdfs e add
I'd rather not remove the line from the startup-sequence. If the ROM is 3.1.4 and the OS installation is 188.8.131.52, then it may still make sense (for OS184.108.40.206) that ROM updates are being installed.
What's pointless is to map the ROM into fastmem when it's being mapped again immediately thereafter.
If you were running OS3.1.4 without a 3.1.4 ROM, it can make sense to use ACATool to load and map the 3.1.4 ROM file. But if it's immediately mapped again in the startup procedure, this task is better left to the OS3.1.4.x.
If you boot OS3.1.4 and do not have a 3.1.4 ROM, then MapROM in ACATool is pointless.
The reset is then caused by C:LoadModule ROMUPDATE from the OS3.1.4 startup procedure.
You can choose which one does the reset; it's either ACATool 2.1 (when an OS3.1.4 ROM file is specified), or the 3.1.4 startup procedure.
The reboot on MAPROM has been removed since version 2.1.
If possible please upload your configuration file IndivisionECSv2.conf from ENV:/ENVARC:.
This is only a wild guess, as there is not much interaction with the outside world except for the configuration that could cause such horrid corruption. Does the config tool work when started booting without startup-sequence?
The new firmware (2.2, flashtool 1.7) is now official.
Oops, the version command returns 2.1, but it's really the 2.2, which is also displayed in the window title. Must be a glitch in the build system, this should be fixed in the next version.
Very strange. Please also redo an auto-adjustment on your monitor.
Also try a different VGA mode.
Do you have the same issue with a different monitor?
It's in the presets, but overwritten by your current configuration. You can get it by "Restore to Defaults" (and switch back using "Last Saved" if need be. Also remember that you can save your current configuration to a file for later reference). Sorry for the new presets are not automatically merged into your configuration. But the new defaults come with slightly changed positions, so it's probably better to start from the new defaults.
Selecting a 1280x1024 VGA mode should not truncate an Indivision 640x512 mode, and you should get a requester to notify you in that case. Please let me know if this can be reproduced with the new version.
Just for the record, I had no issues creating and using a rescue disk with a Gotek. Tested on an A500 with ACA500+
I just uploaded version 2.0 of the software, which includes new firmware 20190308. It allows for more overscan horizontally. Also included are some new presets, including a 50Hz VSync mode. You might give this a try.
Yes, of course config files can be shared.
You can save a backup of the configuration using the Project menu, Save as... and Open.
It's important to understand that the Indivision mode list is searched from top to bottom, and the first mode that matches the criteria will be used. So if it doesn't select the desired Indivision mode for an Amiga mode, then the list needs to be rearranged, or unwanted modes disabled from it. The primary selection criterion is the number of lines on the screen, so for PAL this is min=286, max=287.
To find out which mode would be selected for the current Workbench screenmode, use the Settings menu, "Find Mode to be Applied". To find out which mode is currently active, select Settings, "Find Live Mode". These menu items are now explained in the documentation also.
It's also important to understand that you can edit Indivision modes (and VGA modes) that are not currently being displayed, so on clicking Adjust... a screen is opened with an Amiga mode that is appropriate for testing the respective Indivision mode in the list - but that doesn't mean that this mode will be kept when returning to the Workbench. This is only the case if you edit the Indivision mode that the Workbench is currently running on.
Also note that the Test Mode field should show an Amiga screenmode that is actually useful for the Indivision mode you are editing. So for PAL this would be a PAL screen. This is editable because it makes sense to be able to test a PAL screen in its variants High Res, Low Res, Laced, but it makes little sense to use for example Multiscan for testing a PAL screen. If in doubt, don't change the Test Mode field.
See the monitor's horizontal (24-82 KHz) and vertical frequencies (48-76 Hz).
When you create a VGA mode or copy and change one, make sure that the resulting frequencies are in the range of that monitor.
Here are some settings that may work for 1680 x 1050 @ 60 Hz
Good afternoon Jens. Small bug. If the X-Surf-500 is online. Whdload games wont boot. They go to black screen and stop.
Try setting the device driver offline, like so:
offline x-surf-500-plus.device 0
And back online:
online x-surf-500-plus.device 0
Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser Please create an account and log in to see all content by default. This is a limitation of the forum software.
Don't Panic. Please wash hands.