Posts by Timm

I'm glad I could convey the basic idea. This is an interesting find, of course I have recorded the number of lines for all screenmodes on my 3.1 development system and put them all into presets, to spare people this work. I have no explanation currently.

Quote from BuckoA51

Definitely a bug since I can confirm 640x480 working from other HDMI sources same video chain no issue.

Ok, so let's ask Jens then.

Your both issues/posts are almost certainly unrelated to each other.

From the software side, I cannot answer why I get 640x480 on DVI, but not on HDM*, and cannot even tell if this is a bug.

Regarding the second topic,

you get the number of lines for screenmode detection from testing an Amiga mode - when you return from the 'Test/Adjust' screen on the main window.

Example 1: Select the preset mode "Pre 640x480 MultiscanProductivity" in the Indivision Mode list. Here the 'Test Mode' field should read "MULTISCAN:Productivity", and 'Min. Lines' is 525 and 'Max. Lines' is 526. 526 lines (on a "long frame") determine Multiscan Productivity.

Example 2: Make a copy of the current Indivision Mode by pressing 'Copy' on any mode in the main window. For this mode select 'Test Mode' MULTISCAN:Productivity. Click 'Test/Adjust'. When you return from the test screen, the number of lines on the test screen has been recorded and the field 'Tested' now reads: 526. You can now insert 526 (or better 525) to 'Min. Lines' and 526 in 'Max. Lines', and this mode will furtheron react on changing to Multiscan Productivity. (The difference of one line allows to account for the "short" frames in the Interlaced variant of the same mode.)

Of course it's easier to just make a copy of "Pre 640x480 MultiscanProductivity", the second example is just to demonstrate where you get the number of lines for detecting any mode the Amiga may come up with. Finally, after an Amiga screenmode is recognized, you can assign any viable VGA mode to it. And of course it's a good idea to use (for example) Multiscan Productivity on the Workbench and keep PAL reserved for games.

(But it's also possible to use the keyboard to switch between several VGA modes for the same Amiga mode.)

I don't know about the warranty Id, but you just "drop in" the ACA1234.

Of course you get a lot of options, but software-side installation is not mandatory.

For games, a screen mode with some overscan would be recommended. Games do not always use canonical resolutions of 320x256, 640x512 and so on, but often use more screenspace or ranges that differ from the defaults.

Here on a FullHD device I got a VGA mode "EDID 720x576@50", which I can use with VSync and AutoResolution and which provides plenty of overscan, but the exact modes vary with different monitors and TVs.

You can also use more than one VGA mode and switch between them for Workbench and games using the keyboard, which of course takes a bit time to configure.

Thank you for reporting. We're glad to hear that, I was about to answer "should be no problem", but I'm still struggling to set up a new test machine for these affairs, and I wouldn't have had a Picasso II.

Uploaded it here:

http://wiki.icomp.de/wiki/ACE2#Download

Oops, corrected

The status is that I don't get a picture either via HDM* on a cheap FullHD TV style device.

I used our preset modes "640x480 60Hz" and "640x480 73Hz VGA".

Per HDM* I'm not getting a picture.

Per DVI I'm getting a picture.

I made myself another 640x480 mode in 50Hz, with the same result. I also tried with Auto Resolution, with the same result.

Other modes do work per HDM*. So this made me think it might have to do with specifications, but I didn't look them up.

Version 3.4 of acatool is available, which should support 1mb ROM files for all cards using the ROMFILE option: http://wiki.icomp.de/wiki/ACAtool#Download

In case of the ACA1234, if you want to use 1mb ROM files from the card's flash memory, you also need to update the firmware to version 230124: http://wiki.icomp.de/wiki/ACA1234#Firmware_updates

I recommend to perform the firmware upgrade, because it includes an update to acatool 3.4 on the ACA1234Install volume. The 1mb ROM file I used for testing compresses nicely using the accompanying 'lzocompress' tool. So if you compress the ROM before saving it to the card's flash memory, you save a lot of startup time - and also one valuable ROM slot.

There is no specific 'process' for the Buddha controller.

Our installer is just an option to get past the 4GiB barrier and to install the OS with a few clicks, which gets you started even with older OS versions and today's bigger media. The basic premise is the same as with any other controller for the Amiga.

It's entirely possible that something has escaped my attention when testing with an A2000 and A3000, and I absolutely wouldn't claim that my depth of testing can match that of GVP back in their day.

No, after loading it waits 7 seconds before flashing starts. After that a blinking LED indicates that it's finished. You don't need to press the mouse button. Everything together including booting should not take longer than 30 seconds, and booting from disk is all interaction that is needed. If you don't get a picture then, turn off and on your computer.

I'd suppose the OS 3.2.x HDToolbox handles bigger partitions correctly.

No special treatment, no additional step should be required.

So you did save the configuration to drives using HDToolBox with buddhascsi.device.

Are the drives shown when using the 'info' command?

1. Currently there is no "reset" tool.

2. The rescue disk does not save profiles. The config tool saves the config not only to the Indivision, but also to ENVARC: and ENV: on the WB from where it was used. When after a rescue the configuration on the Indivision contradicts the saved configation on disk, the config tool will alert you of that and you can restore the configuration by simply saving again.

3. What has helped in one instance I remember was to use the config tool with the SAVEAPPLY option on a config file from command line, but I don't know if it is related to this issue. If this helps, this could be placed e.g. in S:User-Startup:

SYS:Prefs/IndivisionAGAmk3 SAVEAPPLY ENVARC:IndivisionAGAmk3.conf

Assuming that the config tool is in the WB's Prefs folder.

1mb ROM files are supported theoretically, there are several provisions in the soft- and hardware. So this is a bug.

Indeed we had no test case so far. If you can provide one or more 1mb ROM files to test against, we can perhaps work on the issue.

Now corrected.

This sounds like you didn't adjust the display width to 960 and height to 540, as suggested in the tutorial. See screenshot there.

This would give you an extactly integral scaling factor of 2, and super crisp pixels and scanlines too.

This would also explain your alleged "clock/phase" problem.

Scanlines intensity can be adjusted with the "Darken" slider in the Test/Adjust window.

It might be possible to get better results by carefully changing the Pixel clock settings in small steps and testing each, but I'm not sure if this is a sound advice.

You must invoke "Restore to Defaults" from the Settings menu to make the mode visible if it's overlain by an old configuration.