Who's Online |
17 user(s) are online ( 11 user(s) are browsing Forums)
Members: 0
Guests: 17
more...
|
|
|
|
|
Re: Mount HDF on OS4?
|
Posted on: 12/12 13:02
#1
|
Not too shy to talk 
|
@broadblues
I'm surprised a def_hdd would be missing. I don't look in there a lot but I'm used to there being a full collection of def icons.
I looked at the binary of my HDD images and some have textual mount info, in the form of a mountlist, after a DOS ID, which I recall is what OS4 or MediaToolbox used to write there. I don't see any help for FixHDF from the Help command but looks like it fixes up geometry information.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
|
Not too shy to talk
|
@sailor Quote: And it is interesting that ub2lb bootlader menu works on Quemu - on real hardware not. It works on the real hardware for which it was intended. It just crashed on my A1/XE when I ported it over. But I recall it wasn't consistent because sometimes it did work, depending on if it was fresh boot or reboot. I just can't recall exactly what but it annoyed me for a month before I tracked down. If only UBoot crashes were more informative.
|
|
|
|
|
|
Re: Mount HDF on OS4?
|
|
Not too shy to talk
|
@broadblues
I do have a def_hdf. Just checked what the tooltypes are after showing all files and getting info on my hdf file. The default tool is MountDiskImage and tooltypes are "DRIVE=IDF0:"
Seems strange to mount from an "IDF0" as I associate that with a floppy but I suppose it works.
|
|
|
|
|
|
Re: Mount HDF on OS4?
|
|
Not too shy to talk
|
@broadblues
It should be as easy as double clicking it. I have some HDF images I tested. They are partition images, so not exactly a "hard drive format" since a partition is a subset, but they opened and mounted fine. I did it the easy way. Opened up a HDF folder and showed all. Double click to mount. I am relying on DefIcons to pick up the tab since they have hdf extension. But a compatible file should open up in DiskImage tool itself. Mine are all standard DOS images.
|
|
|
|
|
|
Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
|
|
Not too shy to talk
|
@FlynnTheAvatar That's good blacklisting would have sorted that out so you could isolate the crash point. Going over the docs, the usage of WindowPtr looks like a bad idea. It's called WindowPtr so should only contain a window pointer or NULL. This is one of those cases where it has too many possible values. While the bug in this case is in ReqTools and must surely be an old one gone unnoticed all these years, it demonstrates a flaw. Only a positive value can be an address which limits it to a 2GB boundary. Of course these pointers were designed around 40 years ago so an "MFP" (or multi function pointer) looks like a great idea.  Given there's so many values that can be there as well as a valid pointer you may need to check specially for 0, -1 and if neither interpret as pointer. The only shortcut I would trust is (!WindowPtr) to check for NULL.
|
|
|
|
|
|
Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
|
|
Not too shy to talk
|
@joerg Quote: If I'm right the DAR (on most PPC CPUs, on 405/44x/46x CPUs it has a different name) of the crash should be 0x00000055. That looks right but you cannot trust the DAR. Anything Reaper spews out about a DAR is corrupt for ten years or more. IIRC it's correct on the serial log.
|
|
|
|
|
|
Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
|
|
Not too shy to talk
|
@FlynnTheAvatar
It looks like you got the call stack you needed. For 68K it's recommended to disable Petunia (from Kicklayout) or blacklist the app in Compatibility Prefs. They really haven't sorted this out. You can't disable JIT emulator without modding your Kicklayout. And blacklisted apps don't have inheritance so child processes still have JIT.
Disabling JIT is recommended as in a lot of cases you don't see the actual code but the the ends of the JIT cache or something.
Edited by Hypex on 2024/12/3 12:27:41
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 11/30 13:08
#8
|
Not too shy to talk
|
@joerg Quote: It can't, it only supports adding it to new images, but if you mount an ISO image with something like diskimage.device it's no problem to create a new one from an existing one. Oh I see. Indirect modification. I likely mounted images to do that if I had any. I tried to use AmiDVD to rebuild a Linux install CD since only my OS4 volumes had enough space back then. But it failed to retain the links. AmigaOS wasn't designed for Linux links so the end result was faulty. Quote: The versions illegally distributed with AmigaOS 4.1 FE (and newer) releases/CDs of AmigaOS 4.1 by Hyperion, despite explicit prohibition to continue including it, are. Not sure about the os4depot and AmiNet versions any more. IIRC it was Contrib. Convenient for the user. Easy enough to download from the depot. But looks like it has an issue with FE Update 1. https://os4depot.net/?function=comment ... e=utility/misc/amidvd.lhaQuote: It's based on El Torito, but IIRC there were some small differences required for AmigaOS 4.x or U-Boot. There were and I figured out what they were in the MakeCD days. SLB as the boot block. And some kind of "AMIGA BOOT" ID string needed. It's too late but I made a mistake when I stated "UBoot doesn't directly support booting ISO9660 off CD". That makes no sense, of course it does. What I meant is that UBoot doesn't directly support booting ISO9660 off USB. For obvious reasons.  Quote: IIRC U-Boot itself doesn't support booting any OS at all, except for Linux with TFTP maybe, but can only load and start the SLB, which then boots AmigaOS 4.x or Linux from HD partitions (FAT, ext2fs, FFS/FFS2, SFS/SFS2, etc.) or ISO 9660 (CD/DVD or USB), or with ub2lb/Parthenope instead of SLB_v2 AROS, MorphOS and Linux, but not AmigaOS from SFS partitions. However using FFS, maybe DOS\0-DOS\5 only, not the new FFS2 DOS\6 and DOS\7 formats, for the AmigaOS Kickstart partition should work with ub2lb/Parthenope as well. That sounds about right. UBoot can scan an RDB or in the least RDB BOOT blocks which are constructed the same way. The simple secret hidden in the boota command. But I looked and ub2lb does have support for SFS. As well as ISO9660. What I cant find is any reference to FFS which is strange. Perhaps UBoot API supports it. One thing ub2lb broke was the QEMU Sam config. I knew why. Some hardware quirk or maybe MMU setup meant a NULL pointer was acceptable. The ub2lb code violated the UBoot API by passing a NULL pointer when scanning CD. I checked the docs and accordingly a pointer must be given. I don't know how or why ub2lb has a "legal" bug that works. But it caused me a month of trouble trying to figure out why it kept crashing my A1 at random when I modified it for a Linux boot menu. Quote: The format of SFS 1.84, the last version from John Hendrikx, is public, but that didn't help much.
The easiest way to destroy any SFS partition is using the broken Linux implementation of SFS based on his public documentation in r/w mode  I didn't recall that. Sounds almost useful. For a boot loader only read support is needed. When I was designing my X1000 Linux boot editor I wanted a boot volume that was readable by AmigaBoot and writeable by Linux. FFS DOS3 turned out to be that happy place. Writes fast on Linux. Quote: In my AmigaOS version of SFS I added some improvements which aren't backwards compatible, except to my own implementations of it (AmigaOS 3.x/m68k SFS, AmigaOS 4.x/PPC SFS and the SLB_v2 SFS code), but not to John's <= 1.84 versions and independent implementations of SFS like the AROS, MorphOS and Linux versions. Yes, SFS has a bit of a convoluted history on the Amiga or post Amiga, splitting up into different Amiga distros.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 11/30 11:31
#9
|
Not too shy to talk
|
@smarkusg
That's all right. It gives me some programs to check out. I last used ISO Master which may not fully live up to the name.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 2024/11/29 11:22
#10
|
Not too shy to talk
|
@joerg Quote: My AmiDVD tool (Enhancer Software, old versions are available for free on os4depot and AmiNet) supports adding the slb_v2 to ISO 9660 images, setting the required flags, etc., and burning them to CDs and DVDs. That's good to know it can modify existing images. I used to do it on the fly when building an A1 OS4 boot image. Are the older AmiDVD restricted to pre-FE? I recall reading about some issue. I have the Enhancer version so not so not so concerned about it. But for my specific purpose I need to inject data into the system area at the first 32KB of the ISO9660 image. It relies on UBoot method of scanning for boot block which is usually after RDB on HDD but it scans for BOOT blocks within a small space for SLB so my chain loader is found instead on USB which then loads in the real boot code from the El Torino boot block. Since UBoot doesn't directly support booting ISO9660 off CD, this transparently works around it and unlike some ISO/USB Linux installers, my method works without needing FAT DOS BOOT CD image hackers. Quote: I never tested it with AROS/MorphOS/Linux-only 2nd level bootloaders like ub2lb/Parthenope, which can't boot AmigaOS 4.x (at least not from AmigaOS SFS partitions), but since it shouldn't make any difference for U-Boot those should work as well, if you only want to boot AROS, MorphOS and/or Linux with them but not AmigaOS 4.x. That's what the issue was. I recall it had some quirk when a friend installed Linux but needed to boot OS4 Kickstart from FFS when his Workbench was on SFS. Provided SFS format was public SFS support could have been added. Parthenope already knew some secrets about booting OS4. It knew what was in the module nodes.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 2024/11/28 4:10
#11
|
Not too shy to talk
|
@smarkusg I wonder if genisoimage or similar can inject data into the reserved system area? Most CD image builders, likely due to using a limited GUI, didn't let you select a file to inject in there I could see. I modified some Amiga program that overwrote the system area of a CD image with a file to get the job done once. A number of of years ago I wrote a small boot code stub I called UBL. Universal Boot Loader. It was to allow USB/ISO CD hybrid images to be created. You could write the image to CD or USB. And it would autoboot off either. It needed to be in the system area so UBoot would pick it up as an RDB boot block for USB booting. IIRC it didn't need to have an actual RDB. It then scanned the USB disk for the boot block, loaded it and launched it. UBL would then check the disk blocks (from USB) for a CD boot block and chain load it in. That then took over and would boot the rest of the USB as if it was on CD.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 2024/11/28 3:37
#12
|
Not too shy to talk
|
@Spectre660
I'm surprised the kernels wouldn't boot. Because one kernel there is only a 5MB image. Geri's A1 kernels were about 13MB in size. The A1 kernels are older format so were not compressed which is likely why but did combine raw kernel with compressed ramdisk inside a raw UBoot image.
Suppose if they cannot be embedded in a multi packed image then possibly a multi raw image should have worked. The kernels were 3.x which matches the last version for A1 Linux. Above that into 4.x and 5.x may introduce too much bloat.
AFAIR both slb and ub2lb use UBoot for booting. So would send it a diskboot command to load image. Then do a bootm to boot it. They would usually do a load to 500000. I think the issue here is GZ breaking it as it doesn't allow enough space and using absolute addresses was bound to break. Did you even try to create a raw image or was the kernel binary too large?
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 2024/11/28 2:49
#13
|
Not too shy to talk
|
@sailor
You got a bit further than I did. I tried to install on friends Sam440. But I kept getting stuck on finding a repo since all the installers are net only. I didn't understand why apart from taking more server space as the internet goes out of date quickly. I spent 2 hours looking for a working PPC repo before giving up. All just ended up in error.
At one point I ended up converting to CD image to USB. Forget why apart from slower CD speed and faster USB speed. But it kept going faulty over USB for some reason.
It is strange only one install menu showed up. I used a modified Parthenope for the A1 Linux installer and I don't recall any missing menu issue. The earlier Sam installers must have given a working system. It installed Parthenope with a menu so that part worked. But the kernel crashed and that only used to happen when a different kernel was booted. I don't see any other OS4 volumes on there.
Not being able to boot from SLB is strange as Geri's kernels for the A1 are large and around 13MB. SLB is used to boot kernel after Debian is installed. Never seen a problem booting a large kernel.
So the dtb is a device tree blob which is really an OpenFirmware object. Whatever firmware is used to boot Linux, it needs this blob to describe the hardware. On UBoot this doesn't exist so it is passed in an extra file. The UBoot on Sam is more modern and accepts multi image kernels as well as DTB to boot.
|
|
|
|
|
|
Re: USB keyboards and Uboot - on a Sam460ex
|
Posted on: 2024/11/27 12:21
#14
|
Not too shy to talk
|
@sailor Quote: For me works best TeraTerm on windows. Putty not bad, is powerful ( excellent for ssh ) but quite complex for serial. TeraTerm is mainly for serial connection ( and partially ssh ), is very easy to setup can send special characters like break easily. With AmigaOS / MorphOS I am using 68k Term Thanks. I'll look that up. Where I have found Windows better is for serial to BT adapters for wireless serial. That works well when testing. Some apps are quirky and don't seem well thought out. But BT is broken on Linux and doesn't work well with the GUI. That was back when I was trying to replace the cable with air. But the devices are expensive industrial units or cheap and buggy PCB boards. Quote: I agree, than USB-serial adapters sometimes picky. For me works only one from two. Allways better pure serial. My workstation has one on motherboard. But today is simplest to buy PCIe serial card, or use cheap old notebook with serial. I must have got lucky. I bought one at swap meet decades ago as it looked useful. Got a long null modem cable. And it worked on OSX without needing to track down drivers. I've since been given some more from a friend but am yet to test them.
|
|
|
|
|
|
Re: USB keyboards and Uboot - on a Sam460ex
|
Posted on: 2024/11/23 6:32
#15
|
Not too shy to talk
|
@NinjaCyborg I take it you never got serial working? Does the Sam have two serial ports and you got nothing out of both? I did set up a terminal in Windows but forgot about Putty so looked for a terminal on the MS store and was shocked how bad they were. The Amiga blessed us with good free software but in Windows, the most popular OS in the world, free software is crap!  I also set it up in Linux but it's a pain as it won't work without root. So you need to stuff around. Better software than I found on Windows but won't work out of the box. However, my main terminal is an old PowerBook G4 with a serial to USB adapter. Running ZTerm as terminal which works fine for my usage. But, because of the adapter, it is quirky. If I leave it all plugged in and shut the lid it will lose connection on wake. So I need to quit ZTerm and reload. I can leave adapter plugged in. But I find I need to the adapter plugged in first and then load in the driver from terminal software. I don't recall if Windows is just as quirky with these adapters.
|
|
|
|
|
|
Re: USB keyboards and Uboot - on a Sam460ex
|
Posted on: 2024/11/23 6:13
#16
|
Not too shy to talk
|
@LiveForIt
In this case there is some issue with interrupts and compositing. I haven't truly got over the Update 2 notfix which introduced the rare but common on my system bug. It's a known issue with Sam 460 and R7 250 as well as RX driver. But my X1000 and R7 250 is apparently uncommon configuration. I've read about some issue with a write back function so could be an OLAND chipset glitch that rears its head.
I ended up testing WaitTOF() with a patch to print calls to serial. On a freeze compose.task is left hanging on WaitTOF(). So there is some interrupt signal missed somewhere. In my case the system is locked up but was still functional internally. Background tasks pinging out to serial still work. So the freeze looks like a graphics lock and not full hardware lock up.
|
|
|
|
|
|
Re: Quake 2 reduced price during time of AmiWest 2024
|
Posted on: 2024/10/26 14:52
#17
|
Not too shy to talk
|
@TheMagicSN Thanks. But there is something wrong with their site. Logged and try to buy on PayPal. Get to Confirmation page and it says click a "Buy" button. There is no Buy button any where.  Edit: Okay somehow managed to fix glitch by going to contact page and then back to cart to try again.
|
|
|
|
|
|
Re: AmiUpdate Update 2.55 (11.10.2024)
|
Posted on: 2024/10/22 2:49
#18
|
Not too shy to talk
|
So I noticed a few discrepancies.
- The latest release is 2.55 but the latest download package is only 2.54.
- The latest download is claimed to be 2.52 on site.
- The latest 2.55 needs to be installed by AmiUpdate updating itself from 2.54 version.
So I grabbed the latest off the website. Installed and it went ok. Reboot. Ran it again and it found a new version. Installed that and reboot again. Now my AmiUpdate is the latest 2.55.
There could be a recurring issue. I didn't see AmiUpdate detect the latest itself. Need to check what I had but it wasn't until I installed the latest available 2.54 manually that AmiUpdate found a newer version.
Also, sometimes I find AmiUpdate checking servers for way too long. Usually finding nothing when there should be some update. I wonder if latest changes cause a slow down in server detection?
Update: (Excusing the pun.)
I updated another volume with the latest AmiUpdate. It had been running 2.49 which is a few releases behind. This confirms my suspicion the issue with AmiUpdate not finding an update to itself is unresolved or has come back. I was stuck on that a few years back.
So I installed 2.54. Reboot and run it. AmiUpdate took a while looking but did not see an update to itself. I then ran a scan and it found an update to itself in the update list. That was strange. Could be a slight bug with latest changes. Well it updated itself fine regardless.
Edited by Hypex on 2024/10/23 0:32:58
|
|
|
|
|
|
Re: CMake 3.29 Native (OS4)
|
Posted on: 2024/10/12 3:16
#19
|
Not too shy to talk
|
@elfpipe Okay got it working. It didn't need to be told where compiler is. But it did need to be told where "make" is. So it was able to complete the build. The make ran without problems. However, I managed to crash it again. I don't know how. I tested CMaking the tinf project from the RAM Disk. It crashed CMake. Does it matter if I CMake direct to list file without a build folder? Looks like it drank a bad coffee from a bad cafe:
Register dump:
GPR (General Purpose Registers):
0: 7E2D52E8 4F2EFDD0 ABADCAFE 00000100 502BD8D0 0200B030 02A8824C 02A8826C
8: 00000000 2F53444B 2F432F6D 0201FBF8 39955959 51033DD8 5EDE09B4 53A4FEC0
16: 02B30000 DFB74240 5958F028 6FFFE300 5101F4A0 5101F020 7D0E9600 00000023
24: 59506760 5101F024 595BA038 7D0E9600 5139AB2C 5139AB2C 4F2F0BA4 4F2EFDD0
Symbol info:
Instruction pointer 0x7E2D53BC belongs to module "cmake" (PowerPC)
Symbol: uv__signal_event + 0x130 in section 1 offset 0x011F6398
Stack trace:
cmake:uv__signal_event()+0x130 (section 1 @ 0x11F6398)
cmake:uv__signal_event()+0x5c (section 1 @ 0x11F62C4)
cmake:uv_run()+0xf4 (section 1 @ 0x11E61D8)
cmake:_Z23cmExecuteProcessCommandRKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EER17cmExecutionStatus()+0x1b3c (section 1 @ 0x476AD8)
PPC disassembly:
7e2d53b4: 81490004 lwz r10,4(r9)
7e2d53b8: 813f001c lwz r9,28(r31)
*7e2d53bc: 81290034 lwz r9,52(r9)
7e2d53c0: 7c0a4800 cmpw r10,r9
7e2d53c4: 40820050 bne- 0x7E2D5414
|
|
|
|
|
|
Re: GreaseWeazle help needed
|
Posted on: 2024/10/12 3:02
#20
|
Not too shy to talk
|
@Greenslade It sounds like you have it all setup correctly. If you have a light on one drive and off on another I wonder if it's getting enough power? A USB2 port is good enough for a USB floppy drive but I'm wondering if an older floppy drive needs more power? Have you tried to run the GW command in a standard CMD line? PowerShell may be too powerful, though it shouldn't matter. By the sounds of it the shell cannot find the path. Are you dragging the exe into the shell window? What if you just run it from the explorer icon? Funny that Windows software doesn't open any windows and needs DOS. Thought we had moved on from this. Might as well stick with the retro PC if you wanted DOS!
|
|
|
|
|
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
