Who's Online |
45 user(s) are online ( 21 user(s) are browsing Forums)
Members: 0
Guests: 45
more...
|
|
|
|
|
Re: HunoPPC
|
Posted on: Yesterday 17:16
#1
|
Home away from home 
|
@khayoz Quote: On a sidenote key F12 is not an Amiga thing! Only with software not supporting all Amiga input methods. Quote: I use an Amiga keyboard(F1-F10) on my X5000. ;) Amiga keyboards support 20 F-keys, F1 (CSI 0) - F20 (CSI 19), not only 10! From the Amiga ROM Kernal Reference Manual: Libraries:
Table 34-6: ROM Default (USA0) and USA1 Console Key Mapping
Raw Unshifted Shifted
Key Keycap Default Default
Number Legend Value Value
------ ------ ----- -----
...
50 F1 <CSI>0~ <CSI>10~
51 F2 <CSI>1~ <CSI>11~
52 F3 <CSI>2~ <CSI>12~
53 F4 <CSI>3~ <CSI>13~
54 F5 <CSI>4~ <CSI>14~
55 F6 <CSI>5~ <CSI>15~
56 F7 <CSI>6~ <CSI>16~
57 F8 <CSI>7~ <CSI>17~
58 F9 <CSI>8~ <CSI>18~
59 F10 <CSI>9~ <CSI>19~
Old ports of unix console software, like the Lynx and w3m web browsers, the mutt E-Mail client or the slrn newsreader (and any other software using the S-Lang library as well) supported all of them. But with current software, no matter if AmigaOS native or ports from other systems, I wouldn't be surprised if only F1-F10 work 
|
|
|
|
|
|
Re: AmigaOS.net
|
|
Home away from home
|
|
|
|
|
|
|
Re: New to Sam460ex
|
Posted on: 12/15 17:34
#3
|
Home away from home
|
@3VILC Quote: Oh damn, that's both cool, and a bit of a bummer. Was hoping to update it to get the slightly nicer looking newer version, as well as boot display from an RX card, but I guess that's no easy task now :( Easiest, but more expensive, option might be to buy the U-Boot chip with the current U-Boot version from ACube and replace your old one with it: https://shop.acube-systems.biz/roms-an ... sam460-physical-chip.html
|
|
|
|
|
|
Re: Minor feature suggestions for OS 4.2
|
Posted on: 12/12 17:18
#4
|
Home away from home
|
@LiveForIt Quote: @taoQuote:I am surprised there was never a UDF
(but if its not, its lack of developers. in any case, many PC's do not come with Blueray/cdroms, the new tread is that everything is downloaded. besides large mvme drives..) Not lack of developers, just lack of payment for contract work by Hyperion, which doesn't have a licence for using it since about 15 years any more. It was removed from the illegal back port to AmigaOS 3.[12].x m68k already and the same has to be done for any new AmigaOS 4.x PPC releases or I'll have to sue Costel. My AmigaOS 4.0 port of CDFileSystem included some minimal UDF support (UDF 1.x only, not 100% sure anymore if it was 1.02 or 1.50 but not enough for data CDs/DVDs/BDs which need UDF version 2.x, but it could read Video DVDs). At that time no AmigaOS video player (MPlayer, DVPlayer, Emotion, etc.) included internal UDF/DVD support yet and depended on the file system supporting it. Current versions of those video players have internal UDF support and an UDF file system isn't required any more for playing Video DVDs with them. A new AmigaOS UDF file system would have to support UDF 2.60 for reading UDF data CDs/DVDs/BDs, just a new UDF 1.x one wouldn't make any sense anymore.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
|
Home away from home
|
Edit: Wrong calculations by me, even only 32KB stack size might be enough for NGFS.
|
|
|
|
|
|
Re: Kiwis: Chance to buy rare AmigaOS 4.1 machines
|
Posted on: 2025/11/28 6:41
#6
|
Home away from home
|
@Hans Quote: I'm not so keen to ship internationally, because it increases the risk of damage. It would be the buyer's risk. Depends on the postal service you are using. For example shipping costs from Germany to New Zealand via DHL are 96.99€ for up to 120x60x60 cm and up to 10 kg packages. Standard delivery, 10-18 days. Express delivery very much more, about 20 times as much and more than twice the value of the X1000 itself  By default it's only insured up to 500€ (about 1000 NZ$), but for an additional 14€ you can get an extended insurance up to 1000€/~2000$ (for the X1000). I guess shipping (and insurance) costs for the opposite way are similar.
|
|
|
|
|
|
Re: Kiwis: Chance to buy rare AmigaOS 4.1 machines
|
Posted on: 2025/11/27 16:40
#7
|
Home away from home
|
@Hans
Perhaps you should add other target countries like Australia, Japan, South Korea, and Europe. Because of the taxes and tariffs introduced by Trump, selling goods to the US has become practically impossible; the taxes and tariffs are often higher than the goods themselves are worth, but the shipping costs for example from NZ to Europe (EU, Switzerland and Norway at least, no idea about the UK after the Brexit) should "only" be about 100 €/200 NZ$.
|
|
|
|
|
|
Re: Flare enough
|
Posted on: 2025/11/24 15:27
#8
|
Home away from home
|
@balaton
I doubt the 460 emulation of QEmu emulates it's alignment restrictions and exceptions.
The problems with alignment of especially FPU accesses, and to a much smaller extent integer ones as well (IIRC only used in WarpOS software, not in any AmigaOS 4.x native software), are:
- The G2 CPUs (603(e)/604(e) in classic Amigas with Blizzard/CyberStormPPC) support nearly anything without exception, partially even odd addresses.
The WarpOS API wrappers like my powerpc.library for AmigaOS 4.x include alignment exception handlers making it work. Very slow of course because of the exceptions, but it's no big problem for executing code created for a 150 MHZ G2 CPU without L2 cache on the much faster G3/G4 800 MHz-1.4 GHz CPUs.
However, it's a problem when porting old WarpOS PPC software to AmigaOS 4.x PPC (which doesn't include alignment exception handlers for such, on most CPUs, illegal accesses), and @TheMagicSN should have had that problem in some of his ports.
- 440/460 CPUs have an additional problem: The 405 CPU core doesn't include a FPU but uses an "external" FPU, even if it's on the same SoC.
FPU accesses which cross a cache line boundary cause an alignment exception on it, for example 64 bit double accesses on only 32 bit aligned addresses can be in 2 different cache lines, which works without any problems and without slowdown for example on G3 and G4 CPUs, but not on 440/460.
The 440/460 HAL part of the AmigaOS 4.x kernel includes an alignment exception handler, but the exceptions make such code very much slower and it should be fixed in the sources.
- POWER CPUs (X1000) may have completely different alignment restrictions than PowerPC CPUs (all other AmigaOS 4.x systems), but I don't know anything about it.
|
|
|
|
|
|
Re: Odyssey 3.0 alpha - how to disable disk cache?
|
Posted on: 2025/11/13 16:12
#9
|
Home away from home
|
@NinjaCyborg Quote: in 2025 does any browser need a disk cache at all? Depends on your internet connection. If you live in a big city with 1 Gbit or more FTTH internet access you don't need a browser disk cache, unless you care about your CO² footprint. If you live in a small village, and/or in an underdeveloped country like Germany (internet access related at least) instead, you may not even get VDSL but only DSL, max. 16 Mbit and in a lot of cases only 768 or 384 Kbit. Or in worst case no internet access at all, neither any DSL nor G3/G4/G5 networks available, only ISDN 64 Kbit or a V56 modem might still be an option - in the unlikely case there are still any service providers supporting it, or satellite internet with a very high latency. If you have a slow internet speed large browser disk caches help a lot.
|
|
|
|
|
|
Re: Problem using Sil 3132 Sata2 controller with X5000
|
Posted on: 2025/11/12 17:40
#10
|
Home away from home
|
@Skateman Quote: We might need to give such a card a try in the Mirari. I have never tested this.
On the other hand..we have SATA and NVME. Even if those are useless on the Mirari: Testing PCI(e) hardware known to have issues on other Amiga PPC systems, like the Sii3152 on classic Amigas (with FireStorm, Prometheus or Mediator) and on the Sam440 as well as the Sii3132 on the X5000, could help to find hardware and/or software (U-Boot) problems on the Mirari.
|
|
|
|
|
|
Re: Problem using Sil 3132 Sata2 controller with X5000
|
Posted on: 2025/11/11 17:03
#11
|
Home away from home
|
@walkero Quote: Unfortunately, they didn't work on my X5000 either, as they are not recognised at all. I tested them on both PCIe x1 my system has, and used Ranger and lspci to see if they are available. Did you check if they are available in U-Boot? Should be something like
pci long
(try "help pci" if that doesn't work). If the firmware doesn't detect PCI(e) devices AmigaOS 4.x can't use them either. AmigaOS 4.x doesn't include any PCI(e) setup code but just uses whatever it gets from the firmware.
|
|
|
|
|
|
Re: Odyssey 3.0 Alpha vs 1.23r5
|
Posted on: 2025/11/10 16:32
#12
|
Home away from home
|
@hotrod Quote: Device running modern webbrowsers not requiering huge amount of RAM was the point here. So just my powermac then and MOS under QEMU. Done lots of browsing there and don't even have 2GB of RAM and it never runs out. With max cache on harddisks using up RAM as well. It's not modern any more at all, but about 15 years ago my AmigaOS 3.9 and 4.x ports OWB (Pleyo's Origin Web Browser) were up to date, except for using a JavaScript interpreter instead of a JIT, and working with most web sites from that time. There were even some masochists seriously using them on an A3000/A4000 with CyberStormPPC (max. 128 MB RAM), or an A1200 with BlizzardPPC (up to 256 MB RAM, but very much slower RAM than on the CyberStormPPC), or a CyberStormPPC with an additional 128-256 MB of RAM with ZorRAM/BigRAM/etc. ZorroIII cards ( extremely slow), and of course in any case additionally using a swap partition IMHO my AmigaOS 4.x/PPC port wasn't really usable on anything with less than 512 MB RAM + at least 256 MB swap partition. The AmigaOS 3.9/m68k port was IMHO only usable on emulators like WinUAE, PiStorm, A600GS (Emu68k), etc., with at least 1 GB of (emulated) RAM. But even for those ports there were some users (trying) to use it on real hardware... My AmigaOS 3.9 port needs more RAM because it was a straight 1:1 port of OWB using SDL without any additional features, while the AmigaOS 4.x port was optimized, used Cairo instead of SDL and had a lot of additional features like a GUI, faster AmigaOS 4.x native font rendering instead of using libfreetype, native scrolling, better, even if smaller, page caches, etc. I guess a current WebKit/WebCore/JavaScriptCore based browser needs at least twice as much RAM as my more than 15 years old OWB ports.
|
|
|
|
|
|
Re: Gemdalus-new AGA game coming soon! It
|
Posted on: 2025/11/8 20:43
#13
|
Home away from home
|
@saimo Quote: * the email address is @gmail.com (the first 11 times there were also dots separators); The GMail SMTP servers remove all dots before delivering the E-Mails, i.e. foo.bar@gmail.com and f.o.o.b.a.r@gmail .com are the same addresses as foobar@gmail.com (additionally foo.bar@googlemail.com and foobar@googlemail.com, etc., and maybe several other google domains). Quote: * the card holder name does not match the one in the email address; You could sue your payment provider for not making any such checks. Depending on the payment provider 70-90% of the fees you have to pay aren't for any transaction costs (0% inside the EU with IBAN anyway, and even outside of it, for most banks which are part of SWIFT, no or only very low transaction fees), but just for insurances for fraudulent payments.
Edited by joerg on 2025/11/10 15:35:12
|
|
|
|
|
|
Re: Odyssey 3.0 Alpha vs 1.23r5
|
Posted on: 2025/11/8 17:32
#14
|
Home away from home
|
@hotrod Quote: So how much RAM does the A600GS got? 4 GB. 1 GB is used by the emulated AROS/m68k guest OS, the rest only available on the Linux/ARM host OS. But how is that related to Odyssey in any way? AFAIK there is no AROS/m68k version of it, only x86 and x64 ones. My more than 15 years old AmigaOS 3.9/m68k port of OWB should work on the A600GS, but probably only if you install AmigaOS 3.9 on it, very unlikely with the included AROS/m68k + SystemV46.
|
|
|
|
|
|
Re: Problems using a SiI3132 SATA2 controller card with my SAM460LE
|
Posted on: 2025/11/7 16:59
#15
|
Home away from home
|
@LiveForIt Quote: Don’t think AmigaOS4.x has a compatibility list at all, its hard to check what you can buy or not, its kind of a mess actually. There is none from Hyperion nor A-EON, but ACube maintains one: https://www.acube-systems.biz/compatibility/compatibility_41.phpProblem: It wasn't updated since more than 2 years any more. Still better than nothing at all, like from Hyperion.
|
|
|
|
|
|
Re: BBoot on real Pegasos 2
|
Posted on: 2025/11/7 16:41
#16
|
Home away from home
|
@nbache Quote: I think it was actually that way in all generations of AmigasOS. Yes, but that's irrelevant for AmigaOS 4.x, even on classic Amigas. Not sure anymore, but at best C:BootLoader (m68k, required for loading the AmigaOS 4.x kickstart modules and booting it) and my L:BootCDFileSystem (m68k, required for installing AmigaOS 4.x from CD to HD on m68k AmigaOS versions) are working with AmigaOS 2.x, maybe one or both even requires AmigaOS 3.x, but definitely don't work with AmigaOS 1.x. Quote: My first one was an A500 with v1.3 (in 1989), and it was certainly case insensitive. My first Amiga, which I got around 1987 +/- 1 year, was an Amiga No numbers. Only later it was renamed to "Amiga 1000", after the A500 and A2000, in the UK additionally the A1500 (= A2000 with 2 floppy drives) were released. IIRC it had 256 KB motherboard RAM + 256 KB Trapdor RAM (+ 256 KB WORM for one of the the 2 Kickstart floppy disks included, Kickstart versions 1.0 and 1.1), and it was delivered with a French/Belgian keyboard with stickers for the different German keyboard layout, because there were no German versions of the keyboard produced yet... Quote: It's "a feature, not a bug" 👍
|
|
|
|
|
|
Re: BBoot on real Pegasos 2
|
Posted on: 2025/11/6 17:12
#17
|
Home away from home
|
@flash Quote: about Emu68k and QEMU I was thinking for a little hardware baed on ARM to run OS4 baremetal at max speed.
Something not possible with QEMU or not with same effiency. Although Emu68k seems to be getting some PPC support now, it's not usable for running something like AmigaOS 4.x or MorphOS with it on ARM CPUs like with a Raspberry Pi 4/5 (let alone even much slower Orange Pi systems, like the one used in the A600GS, A1200NG, A4000NG). It's limited to WarpOS, a re-implementation of it for ARM CPUs, i.e. max. AmigaOS 3.5/3.9/m68k with some WarpOS/PPC support.
|
|
|
|
|
|
Re: BBoot on real Pegasos 2
|
Posted on: 2025/11/6 15:53
#18
|
Home away from home
|
@Maijestro Are you using BBoot on your QEmu A1 XE? If not there are no problems. @smarkusg Quote: It is not BBoot's fault that someone decided that case sensitivity is not important. It was always that way on AmigaOS 4.x, since about 25 years already. The KiCkStArT/KiCkLaYoUt text file and the Kickstart/#?, and often other paths as well if you have multiple versions of AmigaOS 4.x installed, EXEC and MODULE files in it are loaded by the second level boot loader (C:BootLoader on classic Amigas, SLB_v2 from the RDB on AmigaOne and Sam440/460, AmigaBoot.(ub|of) from the SD card on X1000, X5000 and A1222+) from partitions with AmigaOS file systems or from ISO 9660, all of which are case insensitive. Among other parts BBoot is a replacement for the SLB and therefore should work the same way as the originals: case insensitive name comparison in the file loading part.
|
|
|
|
|
|
Re: BBoot on real Pegasos 2
|
Posted on: 2025/11/5 17:28
#19
|
Home away from home
|
@balaton Quote: Case sensitivity does not depend on the unzip implementation. I could uppercase or lowercase the name before comparing but that's additional code and on unix it's possible to make zip with files only differing in case so then case insensitive compare would find a random one. It's better to fix the Kicklayout. There is nothing wrong in the Kicklayout. All AmigaOS file systems usable for loading kickstart modules are case insensitive and both using MODULE Kickstart/SmartFileSystem.kmod and MODULE Kickstart/SmartfileSystem.kmod in the Kicklayout are working on any real hardware without any problems - except for the Pegasos2 using BBoot. The bug using case sensitive comparisons has to be fixed in BBoot instead, both for QEmu as well as real Pegasos2 using BBoot.
|
|
|
|
|
|
Re: BBoot on real Pegasos 2
|
Posted on: 2025/11/3 19:18
#20
|
Home away from home
|
@kas1e Quote: Speed of booting : bboot saves about 10-12 seconds on my peg2, i.e. instead of 40 something like 28-30 for full load up Instead of using a LZ77 based (de)compression I'd try a LZO based one. It's even much worse at compression than LZ77, LZ78, etc. (lha(rc), pk-/infozip, gzip, etc.) is, and I don't know anything about the Pegasos2 SmartFirmware, but the AmigaOne U-Boot is executed with caches disabled, and LZO is much faster, with and without caches, at decompressing than next to anything else is. In a few very rare cases (or even most of of them, if you believe the stats reported by it's authors ) LZO compression and decompression can even be faster than an optimized memcpy().
|
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
