bash64 wrote:
1) Thumbdrive must be in port 0 (internal port) in order to boot. If any other mass storage device is plugged in ahead of it it will not boot.
The port number has no effect on anything USB related except for minor timing issues on checking the ports -- if no devices are connected to the ports in front, there is no difference at all. This must have some other reasons. Are you sure you can 100% reproduce this effect?
2) AsimWare keeps ejecting CDs. AsimWare does not seem to like usb cd drives. I am having better success with CachCDFS under Os 3.9.
No idea. I don't have that software. You could try enabling Simple SCSI in case the device gets irritated by some USB responses (which are usually indeed b0rken).
3) Cannot have CD in drive while booting. Not too unusual as I have had this same issue with PCs. It appears to be an issue specific to certain models of drives regardless of platform.
I am afraid your conclusion is wrong here -- AmigaOS/Poseidon is not a PC/BIOS. But without errorlog, it's pretty hard to make assumptions on what's exactly causing it. Usually, even with a media in the drive, the mass storage class will have difficulties mounting it with a CD filesystem as except for CDrive (phase 5), no CD filesystem can be made rom resident.
4) USB audio eats full 500ma of power. Locks up system even when plugged into a powered hub. A hub that Trident says it likes.
How do you know that it needs full 500mA? Because it says so? If you read the manual, you will have noticed that there is a line about devices often lying about the actual consumption or being self-powered or bus-powered. Anyway, lockups should never occur, regardless of power consumption. Something different must be wrong here.
5) PsdStackLoader never copies to envarc: during the install. This is a definite bug. I keep psdstackloader on floppy because of this.
On successful installation? There are thousands of Poseidon installations out there and you are the first and only one that seems to have this particular issue (that I cannot reproduce here).
6) Installing to a thumbdrive presents a LOT of inconvenient circumstances.
See Michaels response. Updating while running Poseidon has never been supported. The stack stops itself during installation for a reason (e.g. to avoid library version conflicts). I'm gonna remove this stopping for you in the next release, but if any other havoc happens for you or other people, it's definately not my problem.
c) Neither Installer 43.3 nor MUI 3.8 which are required to install the Deneb software are included with the software on flashrom. Makes installing to an os 3.1 formatted drive (non-usb) a little difficult.
MUI is not required to install the software. Trident will work with the NOGUI parameter for the most basic operations like saving the current prefs. MUI, however, is an essential and required third party component for many programs and sorry, it's not my problem to ensure that the user takes care of this for reasonable use of the Poseidon stack. It's not included in *any* software package such as IBrowse, Miami(Dx), Voyager, AmIRC, AmFTP, and dozens other MUI applications.
If a user stubbornly refuses to install MUI and therefore refuses to access 95% of the configuration possibilities (and there are a lot, especially for HID devices), this doesn't sound very smart to me.
And regarding the Installer: This is a standard tool, provided by Commodore/Amiga Tech for software installations since OS 2.0 (I think) and is part of the Workbench setup. Again, I think it's the users responsibility to ensure an up to date and working system setup that hasn't been poluted with hacks and patches that will cause incompatibilities for example. With the same kind of reasoning you could say, we should include SetPatch and the latest Amiga ROM Update files with the Deneb, right?
More later. Share your issues too.
I'd appreciate it if you registered to the highway mailing list for support or send emails directly to me (for the latter, a less offensive tone wouldn't have spoiled our "relationship" in the first place).
I can't write to the a.org forums from work (Wayne! XOOPS sucks in this respect, especially when you only get "An Error occurred: No Error" responses), so its unlikely I will participate here often for the time being.