I used PassMark ImageUSB like written in the documentation.
Ok, thank you.
Even though i never used this software myself, it should be able to write the USB image from Icaros Desktop Light correctly (e.g. no need to correct the header manually).
It's not possible to deactivate HD or DVD in the Dell XPS, just by removing the cables. But this is very annoying.
Yups, i know it is annoying. I always recommend to complain about these kind of things to the manufacturer. It is a simple matter for them to have that supported using some simple BIOS options. Unfortunately, some manufacturers persistently insist on being incompetent.
The dell also has a weird display. It needed a special dsdt.aml to get OSx86 working, otherwise there was only a black display after initializing the graphics card. It uses an MXM laptop graphics card, GeForce 9600GT M. But now it's working, and the display is great, 24" 1920x1200.
Just for my recollection. The dell XPS one is a all-in-one computer that is build to the back of (or even inside) the screen ?
If it is then it is a weird device... not meaning it is bad, just weird from a hardware point of view.
With regards to the dell, i have no clue as how to approach this hardware simply because i never owned such hardware (or know anyone around that has such a thing, so that i would be able to check). Can you share some pictures from the BIOS of that device ?
The old Wacom tablets are using RS-232 with 9600 baud, so they are using the standard serial connector. That's how they can be connected to real Amigas. They have a row of up to 20 buttons on top of the tablet, the pen has two buttons, tip and eraser. There are also a mouse and these cool CAD things with the crosshair pointer for Wacom tablets. And then there's also the 'Wacom Penabled' system, a touchscreen standard which is using the same protocol. It is used on various older laptop-tablets, f.e. the Thinkpad x61t. So, porting the Wacom driver from Amiga 68K would be an interesting idea. Every PC has an onboard RS-232 port and since USB they're mostly unnused.
I asked because i do not know anything about graphic tablets at all, other then they exist and there were some of them supported on Amiga. Hence me asking
As far as i can tell, indeed that would require a specific driver to be written for AROS.
I'm an expert in multiboot systems,
I am sure you are (i am certainly not), but right now you seem to unable to even boot a single one of them.. namely AROS
The point there is to first make sure you have a working USB-pendrive, no matter what hardware it runs off. That way you are able to at least cross one hurdle of your list of things to check.
That's why the AROS incompatibility is really annoying for me. It's the only OS I want to install, but it doesn't accept any of my hardware.
Well, it is annoying to have to dig through hardware that you do not own yourself
The zotac board you have should be fully supported, and you should have no issues at all booting AROS from a USB-pendrive from that. All the BIOS options are there: able to remove/add storage devices, boot order, boot priority, IDE legacy mode, USB legacy mode, USB storage emulation, able to shut-off acpi etc. etc.
As said AROS is able to boot from almost any hardware. The hardware compatibility list is just a small list of things that are reported that do work. And even when it is listed as not working then it is sometimes possible to work-around things, either by replacing some hardware or otherwise.
To give you an example: i have a board that is fully supported by AROS. Even the graphics card is supported. Yet, the darn thing runs havoc. Why ? because there is one tiny little issue in that the graphics card is usually connected internally because it is a laptop mobo, while my board was stuffed into a netbook- case with an external screen adapter. AROS boots, tries to detect the graphics card (which goes fine), and then switches the display output to the internal header. which is not connected on my mobo, is then unable to receive a signal from the monitor, and decides to throw in the towel.
That does not mean that my hardware is unsupported or that the HCL is wrongfully listing the hardware as compatible. It is just one of those little things that requires attentions from a developer,. But even then i cannot expect any developer to pay attention to it because (s)he would have to have the exact same hardware to be able to reproduce the issue and being able to address this specific situation. Same goes for the many many many revisions of a specific audio codec or wifi chipset.
btw, i still would have to investigate things with regards to your 3-th mentioned hardware setup...