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.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
...which is why we're hosting a different version of CacheCDFS in our Wiki.
Not really. This sounds more like some mashup from different installations.
CacheCDFS 60.5 from our installation DOM should be the right one, together with the mountlist entries in Storage.
This was subject to some major cleanup in the latest software package. There should be no connection to buddha_atapi.device anymore in our software package, and I doubt we should have v42 around.
The only other improvement I could wish for with the ACA 500 Plus is a more current file system with the included WB 3.1 install. Long filenames are a must with WHDLoad. It’s a pain to rename files to extract them on the A500.
The filesystem PFS3 is pretty modern, maybe the most modern available.
With the utility setfnsize you can increase the filename length to up to 107, I guess.
Please check out this thread: https://eab.abime.net/showthread.php?t=91088
Somebody says "Super long filenames create all sorts of trouble in many programs (like DirWork). Avoid.", but I haven't tried it myself yet. I have no opinion on that.
The choice of internet software for a plain Amiga 500 without acceleration is limited. By far the most important one for me would be a mounter for a network filesystem. We have included two mounters, for Samba and NFS, in the package. They are covered by the documentation and example configurations.
The problem with nfs and smbfs is just that they are increasingly going out of fashion because everybody else considers the protocols too old - which is actually not an issue inside a trusted home network. There is a new Samba mounter available which supports newer protocols, but it has got other problems.
We have identified this problem.
For downloading software I can now heartily recommend the program Lubricator 2.x from Aminet and the iComp share under X-Surf/Extras . You can even launch it from there.
With this program the whole software/demo archives of Aminet and Pouet are available to you with a graphical user interface, even on an unaccelerated Amiga 500 with at least OS 2.x.
But our support has to end at some point. There are innumerous ways and solutions for many protocols such as IRC, FTP, mail, I guess even on a plain 68000, many fairly outdated, others still totally recommendable. But it's difficult to keep track and to give recommendations. This is something more for Amiga user forums.
Also it shouln't be too easy on a 68000, we still want to sell some accelerator cards. 
With a 68030 browsing the WWW is just barely possible. The only problem is, there are few websites which limit themselves to such old specifications that it's any fun. But there are some fringe solutions even to that, for example by setting up all kinds of funky proxies.
- What you describe as "software messy" could be a graphics refresh issue with OS3.2. Do you have the possibility to use ROM 3.1 during installation? This is what I'd suggest for various reasons, at least with our installer (see the README for a more lengthy explanation).
- That the CDROM is listed in the menu, but cannot be clicked, is as expected. This is just for information and for you to identify the devices. When installation with our installer is successful, the CDROM support should be installed in the system, and you can activate it with the device icons in SYS:Storage/DOSDrivers (and move the appropriate icon to SYS:Devs/DOSDrivers if everything works as expected.)
- This message "device needs updating" in itself is pretty harmless. This is equivalent to the update that HDToolbox complains about when a device has been added or removed, or the order changed. The idea behind this was that in times with slowly spinning up harddisks the time for searching bootable devices could be reduced. It's some kind of "software-side bus termination". Other tools like HDToolbox should be affected and complain in the same way.
The question remains why the update with our software didn't work.
Indeed, an installation is not needed for CDROM support. You can also activate a CDROM by clicking the appropriate device icon in Storage/DOSDrivers. (However, for this to work, the system must have access to BuddhaCDSupport/L/CacheCDFS. So if you haven't installed a system with our installer or didn't boot from the DOM, you need to copy CacheCDFS to SYS:L .)
In face of all this positive feedback, here some self-criticism:
The CF slots are delicate and prone to bent or broken pins. Please treat them very carefully. Do not change cards too frequently.
Changing the ACA500+ between A500s is also prone to failure. I've managed to misfit an ACA500+ so unluckily (don't know how) that it destroyed the ACA500+ and the Gary chip. Please be careful when changing the ACA500+ card and CF cards on it, so you can enjoy it for a long time.
The solution is, in my opinion, to order an X-Surf-500 to get rid of all the mechanical stress. I honestly believe it's worth the extra money.
I recommend that the mountlist entries go to Storage first. Then, when the right ones are working and do what you want, you _can_ move the respective entries to Devs for mounting them on system boot. As long as you're having problems, please park them in Storage, now, and also other devices in Devs/DOSDrivers that look like they might be CD-related.
Then, please perform a version check on CacheCDFS:
# version full file L:CacheCDFS
BuddhaCacheCDFS 60.5
It looks like something else is installed with regard to CDs. Please try to identify things in Devs/DOSDrivers, WBStartup and S:User-Startup that might interfere, and move them out of the way. There is no "3.9" related text supposed to appear with Buddha's basic CD support. The basic support requires only buddhascsi.device (in memory, from the controller itself), L:CacheCDFS and the right mountlist entries. The tools in BuddhaCDSupport are useful, but optional.
Basically just CacheCDFS from BuddhaCDSupport:L/ and mountlist entries in Storage/DOSDrivers.
The first goes to SYS:L, the second to SYS:Storage/DOSDrivers/ .
In addition to that, you can copy CDFSPrefs to SYS:Prefs/ .
There's not much magic in what the installer does.
Hm... no idea so far. Would we know anything else, something smaller, using IPX besides ADoom?
Our network drivers are SANA2, and in no way special.
When it just doesn't start, I'd suspect some setup problem.
On our driver's side you might want to try the options
DEBUGLEV 1
to see if the driver gets initialized and if there's some activtity, and
NOAMITCPOPT 1
- just to be sure, shouldn't matter if AmiTCP isn't used.
Yes, this could be consistent with the 'Failsafe'-jumper being set.
Please remove the jumper from the ACA1221lc, it's normally not needed, or not anymore.
I can't confirm this. This works as expected from commandline and GUI. I switched forth and back several times. With the 14MHz setting I have fastmem. Writing the config to flash was no problem.
It cannot be seen on the photo, which screenmode was that?
Now you're confusing me! Ok, I'll have to set up the machine again, I wasn't entirely sure (it has been a while). But yes, I think so, we've had CPUON and CPUOFF even before the ACA1234.
With the latest ACATool v3.4 and Kick3.1 I have no issues switching back and forth between 68030 and 68020.
If 3.1.4 is the only difference, we'd have to narrow this down to 3.1.4 or things installed in 3.1.4 (such as mmu.library, perhaps). You could for example try booting without startup-sequence and use acatool cpuoff/cpuon there.
Chances might be increasing if you're looking for devices with a *DMI port - so including what is called TVs nowadays.
The good thing about *DMI is that according to specifications 50Hz must be supported. That doesn't automatically mean that VSync is going to work. I might have been lucky, but for testing purposes I acquired the cheapest "TV" I could find, and it instantly gave me better 50Hz/VSync results than any declared "PC monitor" with VGA/DVI/DIsplayPort connectors.
I'm currently not sure in how far the AUX port plays into it. Some points:
- The latest menu version is 0.146. An improved installation procedure with regard to OS 3.2 has been added in this version. For this to work, it is also required to update the installer to version 1.5.
- With this version, using a 3.2 ROM file is not required, as you can install OS 3.1 with our installer first, and then install OS 3.2 over it, all under 3.1 ROM. In fact this is the procedure I recommend, as it gives you an installation which is more flexible with regard to the ROM you are using: Both the resulting 3.1 and 3.2 systems can be used under both 3.1 and 3.2 ROM.
- Another question would be which version of OS 3.2 you are using. The version we were testing against was 3.2.1.
Although we do not directly support OS3.2, we still try our best to work around its issues, and provide a pleasant user experience.
See also OS3.2 annotations here: http://wiki.icomp.de/wiki/ACA500plus_Firmware
- You should first try different VGA modes for output. While the default "Pre 1280x1024 60Hz VESA" should work, "EDID: 1280x720@50", which I received from the monitor, gives me a splendid picture.
- You can try scaling and panning in the main window's 'Test/Adjust' screen: When over the 'Adjustments' window, hold the right mouse button to scale, and the left mouse button to pan the display.
- The jitter may be a different topic. On one of my A1200s for example I have to set the checkmark 'CCKLine Pull-Up' in the Advanced settings section to get rid of display issues on some modes such as PAL SuperHires.
Here you go. 1:1 profile that works perfect for BenQ BL702A.
That's really a fine config with a BenQ BL702a.
You might also want to take into account that the Indivision mode list is traversed from top to bottom when an Amiga screenmode switch takes place. The first Indivision mode that matches the lines and resolution mode criteria will be used. There might now be an overlap between line number ranges in your list. This isn't really a problem in itself, but might be confusing. In that case, you can sort your favourite modes towards the top of the list, and/or disable unwanted modes.
