@All

Is there anyone who tried to setup real (but virtual) serial port when use qemu ? I just tried to use com0com which create for me virtual com4/com5 ports, but when i simple do for qemu "-serial COM4" and then putty on com5, i can see that things start to throws on com port, through slower than expected, and after a while simple freezes.

Is there better alternatives or maybe i do something wrong ?

The point is to have EXACTLY com port after i run qemu to which i can connect via putty/scripts to acts with it as i act with real serial port.

Thanks!

@AmigaOldskooler

Gotta start somewhere eh Thanks for joining in! Hopefully more will start playing as May comes around

@balaton
Quote:
I corrected the post; it was translated incorrectly—my apologies. It’s not better; it’s actually worse—it’s slow and doesn’t have 3D yet, but it would make installation easier.

@joerg
Quote:
How could I do that if I don't know what the graphics/rtg library does and there's no source to check? But the GfxBench2D test just copies blocks on the screen around and there's a difference in that with ati-vga and sm501 so I'd try to understand that first.

@smarkusg
What binary patch and what GPL driver? Doesn't it use the 3dfxVoodoo.chip driver that comes with AmigaOS? Then you should not need any patch for that but it may need an actual 3dfx ROM for the card which may not be distributable again. If it comes with a separate driver then does 3D work? If not what is better about it than other 2D cards? Maybe it's slow because you have NOBLITTER=Yes so it's just used as a frame buffer? I think Voodoo is quite limited by the capabilities of that old card so it's probably a dead end anyway.

Maybe amigaboot does not check bootable flag because that's for something else. A bootable partition is what can be SYS: but the Kickstart files can live on a separate boot partition like on pegasos2 where the firmware can't read the file system used by AmigaOS so it may need boot a partition for Kickstart. That boot partition is probably not set bootable because it's not the SYS: volume but amigaboot still has to read Kickstart from there.

@balaton
Quote:
Yes. There is a problem with that. Some minor issues have already been fixed.
The driver isn't fast, but since it's probably the only one under the GPL license, it could be added (created) as a binary patch to the PEG2 and A1 installation discs. After purchasing the license,
you can download the ISO file, add the binary patch (Add monitor preferences), and boot the system.
Any System updates do not interfere with the operation of the system or the Voodoo3 driver.
Even if the Voodoo3 is slow, you could upgrade the system to U3 via updates and then install whatever you want.


One issue is the patch for QEMU. For now, the author is creating binary versions of QEMU (unofficial)
Time will tell how this plays out

@kas1e

Quote:I believe that depends on whether you have set the NV variable "bootable_only" (to y, Y, or 1) or not.

Best regards,

Niels

OS4 version is in Beta stage. It seems to run great so far.

Donation to PayPal -> Beta Version.

For 68k Version I *hope* a rewrite to SDL1 will bring enough speed to make it viable (we will see if this is success).

Here is my first contribution to the contest.



1244 points. Not much, but a start, hehe.

@balaton
Quote:You should investigate the reason for the way too low VRAM usage with ati-vga.
graphics.library and the p96 .card/.chip drivers do support an unlimited amount of bitmaps swapped out to DRAM, but for using any of the HW accelerated functions of gfx drivers the bitmaps have to be moved to VRAM first, and constantly swapping bitmaps between VRAM and DRAM can explain huge slowdowns, especially for operations using large bitmaps.

@Hypex
Quote:What an ugly mess...
And i thought the old "SLB" method used on the AmigaOne SE/XE/µA1 and Sam4x0, which can no longer be used on newer systems for various reasons, was a bad hack already
But compared to what AmigaBoot.(ub|of) seems to do, like ignoring the RDB bootable flags of the partitions, it was an easy method that actually worked, across all possible boot methods supported by the hardware and firmware (TFPT, PATA, SATA, USB, CF, MicroSD, ..., supporting lots of different file systems, not only at least 8 AmigaOS ones but for example ext2fs for Linux booting as well, and ISO9660 El Torito for any OS, etc.)
Even the much worse method used for booting AmigaOS 4.x PPC on classic Amigas, with AmigaOS 3.0/3.1 m68k used as "Firmware", seems to be better than what AmigaBoot is doing on the Peg2, X1000, X5000 and A1222+ 🤷

@TSK

Quote:

That's because the BootDevice file species the device to boot from. In other words from where to boot Workbench. Since amigaboot.of is working at the Kickstart level the boot process hasn't got that far yet.

I can see it makes no sense from a user point of view to include non-bootable devices. Of course the boot flag predates a bootable Kickstart. I don't see any obvious variables it looks for. Perhaps they would consider adding this as an option.

@kas1e

Quote:

So I plugged it all back in and tested again. In fact I only removed my main boot drive and left all others connected. The other SSD connected only has one OS4 volume, all the rest are Linux. It got stuck on boot again. I see the same two issues occurring. Which are the USB drive is not being detected by mass storage so that prevents it being the boot drive. It explains why it keeps booting to HDD after loading Kickstart off USB. However the old boot error about missing Workbench doesn't show up. I guess it just picks the next in the boot list.

I'm not sure why a HDD full of partitions would mess with mass storage. Unless there is some limit to bootable volumes. I do have a few different Kickstarts I can test. Not that many, Update 1 may not be there, but Update 2 and 3 are. Update 3 may be too new so I may need to drop back down to Update 2. Easy enough. But a pure USB loading test would be better. I still have the ISO USB also.

As to my device setup, I have mostly set this up as standard. That is what SATA port they specify to connect HDD and DVD. I know others have changed but I left mine as default ports as I didn't want any trouble. The only exception to this would be I have two optical drives, or in my case two Bluray drives, with one being a writer. And now with an SSD all ports are filled. I don't have any extra PCI cards except an RT8169. And don't have a CF card. Don't think I ever put one in.

Quote:

I expected as much. So it ignores any boot flags. Perhaps because the boot flag is designed for DOS boot and it's a level earlier loading Kickstart. Still seems inconsistent from a user perspective.

I wonder then if some variable is needed to configure your patch? For example to apply PIO/DMA patch but disable adding devices. So far as I know arguments cannot be parsed on command line, unless there's a way, so NVRAM variable my be needed.

Also, I notice your patches don't exit with the usual CFE exception that clears the screen. So you must really hook into the CFE routines for console and exiting. I'd like to write a binary that doesn't cause an exception when exiting normally with a 0.

It looks like dopus5.lha was renamed to dopus5byai.lha and has inherited the download count of the former archive, and dopus5.lha is a fresh upload with no history.

Edit: That has been fixed.

Neither of the archives have any comment history or snapshot images (dopus5.lha had comments and a snapshot image). There's possibly vote history that is older than 30 days that can't be seen by us that might be in the database somewhere and assigned to the dopus5byai.lha archive.

@samo79
I would suggest, if you continue to upload the archives, use the project's name, which is "dopus5allamigas". Just an idea.

@kas1e

No no do not worry, i did not set any password, admin should replace it quickly

@samo
I uploaded my version back with password set, in upload query now. Now i do not know if it will be replaced back by admin or not, and if you set a password when replace it or not.

(Ignore this message. Mods can delete this, obviously)

@TSK
Quote:

And it was, just without patch your other HDDs wasn't recognized by CFE.

Quote:

Not BootDevice file, but Kickstart/Kicklayout from parition which you do not want to be listed in amigaboot from those HDDs which now recognized in CFE.