Who's Online |
51 user(s) are online ( 34 user(s) are browsing Forums)
Members: 1
Guests: 50
Elwood,
more...
|
|
|
|
|
Re: A1222+ issue with CD/DVD drives?
|
Posted on: 5/16 16:36
#81
|
Quite a regular 
|
@graff @dfstudios
Ok, I understand, thanks for the advice. I have decided to use an external USB HUB with a separate power supply to make sure there is enough power available. I hope this solution works.
Also, yesterday I was able to buy an RX 570 ITX graphics card for the ITX tower with 8GB at auction, so I can test this card in addition to the RX 550 4GB ITX to see if there are any speed differences under AmigaOs4.1 with these cards. I will open a separate thread for this test later and whoever wants to can then participate and publish their results as well.
Which tool is best suited to perform graphics card tests under AmigaOs4.1 2d/3d accelerated?
The a1222plus supports DDR3 SODIMM 64 bit interface
400Mhz, but is it also possible to use SODIMM with 1333/1600 MHz, or will the system then become unstable? I have read that this board has been tested with the SODIMM 400MHz as standard configuration with AmigaOs4.1.
Edited by Maijestro on 2024/5/16 16:56:14
Edited by Maijestro on 2024/5/16 16:57:12
|
|
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/16 15:19
#82
|
Just popping in 
|
This thread is a mess to follow so sorry if i'm pointing out something that's already been talked about or if i miss some information.
If your partitions is SFS formated it's very important that your's usb boot media contains the "updated" sfs that supports the X5000.
The OS4 cd does not have it for sure so you can not boot from it and access any SFS partitions.
I have no idea what this "pendrive" that you talks about contains but it does for sure sounds like it also does not have the correct version as the behaviour sounds like how SFS partitions would behave if wrong version was loaded.
|
|
|
|
|
|
Re: Tracing
|
Posted on: 5/16 15:10
#83
|
Just can't stay away 
|
@kas1e Quote: So question which noone were able to answer me: why there were needs to create callhook() at all in amiga.lib, when, intuition has already callhookpkt, and all ut needs is callhookpktA(), and be done with it. CallHookPkt() was added in utility.library V36 (AmigaOS 2.0), using the libamiga.a CallHook() instead was required for software which should work on AmigaOS 1.x as well.
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/16 14:29
#84
|
Not too shy to talk 
|
@MamePPCA1 Quote: As I told before my AmigaOne X5000 resets after the splash screen.You can read it probably on my first posts. Ah yes, it's on the second page. Forgot about that. Ok, so that proves the partitions are still there or at least the partition holding the Kickstart. Which should be on DH0. Quote: Using Media Toolbox. But I wouldn't recommend it without a backup. It will delete all records of your partitions. Quote: And as I said before my HDD partitions shows on Media toolBox.3 in total. I can't think of any reason for them go missing. Usually there would be some sign like an NDOS icon on Workbench for any corrupt partition. Is it the same in the CLI? So if you run Info in a shell window is there also no sign? Assign is another command that will give info. Quote: Partition Wizard doesn't run.I tried before and no luck. The pendrive should have a compatible version. It may just be a basic recovery Workbench without any Enhancer fixes or just Radeon driver. While it's usually all pre-installed by a dealer that only works if the system doesn't break. Which in reality a recovery system should be able to fix. However your problem is unusual. These days an X5000 is offered with an SSD drive. Currently Amedia sells it with one. What isn't ruled out yet is the HDD going faulty. The problems you experienced could be a symptom of that. The first HDD on my XE played up within a few short years.
Edited by Hypex on 2024/5/17 4:44:23
|
|
|
|
|
|
Re: developing amiga 68000 clone
|
Posted on: 5/16 12:01
#85
|
Just popping in
|
@HypexQuote: Hypex wrote:@kerravon
Quote:It can be, yes. But e.g. I have a version already that uses UEFI for x64 - is that considered to be hosted? Even when my executable is called bootx64.efi and the EFI shell is not used.
Well I suppose it could be considered hosted if it relies on UEFI for its work and not for bootstrapping.
Ok, and what about an OS (e.g. PDOS/386 and MSDOS) that relies on the IBM PC BIOS to do its work? And what about an OS (e.g. z/PDOS) that relies on intelligent hardware (ie mainframe hardware) such that there isn't a lot of work to do to create a CCW to obtain data from a device? Regardless of your answer to that, if you think using UEFI is "cheating", then there is no issue replacing the pseudo-bios layer that PDOS-generic relies on with direct access to hardware - ie partially (and pointlessly?) duplicating UEFI. I just haven't had a reason to do that (apparently?) pointless work. It hasn't been a priority. Right now my priority is to have a mini Amiga clone so that at long last I can actually test my Amiga executables without having to ask someone else to test them for me. Quote:
Quote:I was advised that D5 and above were "free":
Okay I see, because of old BCPL ABI. Well that's only relevant if you're reliant on it being compatible with OS1.3 and below. Code can easily be backwards and forwards compatible. Assembler programs relied on A0/D0 containing the CLI arguments. As did C startup code populating argv/argc. This changed with DOS ReadArgs() as it didn't use A0/D0 as a source but they were stored elsewhere. However the convention was for them to be in both places in OS2 and above. That thread has lots of discussion. 
Early OS commands used the BCPL interface. But it isn't needed for any code. Although it provided a direct interface to DOS in a quirky BCPL way any code can just open dos.library and call functions the normal way. However, I did find that functions like ReadArgs() made public in OS2, were actually existent in early forms and callable in BCPL but it wasn't publicly known.
Ok, I was excited about this, as I don't like having to rely on registers at startup. However, I realized (incorrectly?) that in my case it doesn't matter. I need to get the number 4 (ExecBase) from somewhere (noting that the number will no longer be 4 when run under qemu-m68k Linux or Atari or whatever, so I can't see anything to be gained by switching to using ReadArgs. Note that I'm doing something similar for Linux itself - I don't get argc and argv from the stack - at least not as a first preference. I try /proc/pid/cmdline first instead - which normally always exists. That allows PDOS/386 to run certain Linux programs without needing to construct the odd stack. I could put the (alternative to) the number 4 on the stack, which would allow standard C code to read it, but I would still need a flag of some sort to indicate that an alternative ExecBase has been provided. So the high bit in D0 seems to be as good as anything else, and I'm stuck with needing assembler code. Or does AmigaOS already put something on the stack that I could rely on and detect? Or any other technique? Quote:
In any case, if PDOS is an OS, this shouldn't matter. Except for PDOS bootstrapping itself under AmigaOS. But, will there be a PDOS, that simply uses DOS to bootstrap and then takes over? Like Linux would do. Or, will PDOS rely on the OS as a BIOS of sorts, so run hosted and need AmigaDOS underneath?
All those scenarios are possible depending on what user requirements are. However, the one that I am more likely to code personally is the one that uses AmigaDOS as a glorified BIOS. Because I may not be able to access the hard disks from PDOS otherwise, because the hard disks may require device drivers that are no longer supported and that there is no source code for. Replacing that for every bit of hardware is not really something I wish to do. Perhaps if there was a user requirement and a user willing to pay for development of that. But for me as a hobbyist - unlikely. Quote:
Quote:However, my ELF is not executing on qemu-m68k. Is there a "note segment" required for Linux?
Not that I'm aware of. But, I haven't used m68k Linux either.
I can confirm that it is NOT required - the technical issues were resolved. One of the header sizes was being set to an incorrect value. Quote:
Quote:gccami is used to produce assembler. asami is used to convert that to Amiga hunk object code (no other choice I think). ldami will convert that into a hunk executable (only choice I think - maybe a.out too?). Or now, pdld will convert the Hunk object code into ELF (the only choice currently, but Hunk output is expected to be added in due course).
That's a few layers there! Hopefully you can simplify that down the line.
In one aspect, that IS simplified. Restricting each program to reading text or binaries files and writing text or binary files means that each program can be C90-compliant, as reading/writing files is something within the scope of C90. Quote:
But, compiling was always assembling parts, generating object code, then linking them all together into a final binary. Common object files were not stored as common HUNK but as a related format. And lots of libs were an archive of object files. So a final linker generating ELF is not unreasonable.
Yep, proven technology now.
|
|
|
|
|
|
Re: A1222+ issue with CD/DVD drives?
|
Posted on: 5/16 10:51
#86
|
Just popping in
|
@Maijestro Quote:
The DVD/RW drive I want to use is very simple and requires very little power V5 with 1.6A it also has no external power source to connect.
Just remember that USB2 standard specifies 2.5W for USB ports - i.e. 0.5A per port. You may be able to draw more if there is no overcurrent protection in the hardware, but it's not required to deliver more than that, and may even turn off power to the port if you draw too high a current. Also, the USB stack may refuse to attach your hardware if it deems that it will drain the USB bus power budget. Regards, Thomas
|
|
|
|
|
|
Re: developing amiga 68000 clone
|
Posted on: 5/16 10:34
#87
|
Not too shy to talk
|
@kerravon Quote: It can be, yes. But e.g. I have a version already that uses UEFI for x64 - is that considered to be hosted? Even when my executable is called bootx64.efi and the EFI shell is not used. Well I suppose it could be considered hosted if it relies on UEFI for its work and not for bootstrapping. Quote: I was advised that D5 and above were "free": Okay I see, because of old BCPL ABI. Well that's only relevant if you're reliant on it being compatible with OS1.3 and below. Code can easily be backwards and forwards compatible. Assembler programs relied on A0/D0 containing the CLI arguments. As did C startup code populating argv/argc. This changed with DOS ReadArgs() as it didn't use A0/D0 as a source but they were stored elsewhere. However the convention was for them to be in both places in OS2 and above. That thread has lots of discussion. Early OS commands used the BCPL interface. But it isn't needed for any code. Although it provided a direct interface to DOS in a quirky BCPL way any code can just open dos.library and call functions the normal way. However, I did find that functions like ReadArgs() made public in OS2, were actually existent in early forms and callable in BCPL but it wasn't publicly known. In any case, if PDOS is an OS, this shouldn't matter. Except for PDOS bootstrapping itself under AmigaOS. But, will there be a PDOS, that simply uses DOS to bootstrap and then takes over? Like Linux would do. Or, will PDOS rely on the OS as a BIOS of sorts, so run hosted and need AmigaDOS underneath? Quote: However, my ELF is not executing on qemu-m68k. Is there a "note segment" required for Linux? Not that I'm aware of. But, I haven't used m68k Linux either. Quote: gccami is used to produce assembler. asami is used to convert that to Amiga hunk object code (no other choice I think). ldami will convert that into a hunk executable (only choice I think - maybe a.out too?). Or now, pdld will convert the Hunk object code into ELF (the only choice currently, but Hunk output is expected to be added in due course). That's a few layers there! Hopefully you can simplify that down the line. But, compiling was always assembling parts, generating object code, then linking them all together into a final binary. Common object files were not stored as common HUNK but as a related format. And lots of libs were an archive of object files. So a final linker generating ELF is not unreasonable.
|
|
|
|
|
|
Re: Tracing
|
|
Home away from home 
|
@joerg
Talked with some os3/os4 devs, to find out, that back in 1990, in the internal times of creating v36-38 , they firstly create callhookpkt() for user based callbacks. Then, after some months, were created independently callhook() and its callhookA(). While, all what they need is to create CallHookPktA() stub and that all.
So question which noone were able to answer me: why there were needs to create callhook() at all in amiga.lib, when, intuition has already callhookpkt, and all ut needs is callhookpktA(), and be done with it.
Amiga.lib ones were faster ? Less code ? But then it lioks like more code instead (put stuff on stack, back, etc). I can understand if CallHookPkt() were created after, for exactly avoiding of more code, but by history commits of the os3 it looks exactly in opposite: first one they create callhookpkt, and then after few months, internaly, they create callhook/callhooka in amiga.lib, like, it need them more. For end user it was a single push release of all 3: callhookpkt in utility, and callhook/callhooka in amiga.lib
What was the logic behind of such reversed and doubled work ?
On os4 this another story: callhookpkt were choicen, expanded to have emulator check, and callhook() added for easy porting from os3 (which developers back in past by some reasson prefer callhook from amiga.lib doing job). Probably it worth of bugreport to ditch few remain callhook() in os4 components in favor of callhookpkt(). Those 16 assembler instructions on emulator check cant bring any real overhead probably ?
|
|
|
|
|
|
Re: AmiStore problems
|
|
Not too shy to talk
|
@AmigaOldskooler
It did help. Thanks.
|
|
|
|
|
|
Re: VARARGS vs TAGLIST
|
Posted on: 5/15 20:29
#90
|
Home away from home
|
@Hypex Fix length, is not that good, I agree alligment is issue. making it smaller then 32bit, like 16bit or 8bit will sure create alligment issue, but sizeof(char) // perhaps something like. #define sizeof_alligned(x) (sizeof(x) & 3 ? ((sizeof(x) + 4) & -4) : sizeof(x))
Char *ptr = ….;
type = *((uint32 *) ptr); ptr+=4;
while(type != TAG_END)
{
switch (type)
{
case is_64bit_value:
value64 = *((uint64*) (ptr)); ptr+=8; break;
case is_32bit_value:
value32 = *((uint32*) (ptr)); ptr+=4; break;
}
type = *((uint32*) ptr); ptr+=4;
}
The natural alternative to tag lists and var_args is overloaded methods. by definition function pointer is almost the same as virtual method, it’s a small jump from current implementation of AmigaOS4.1 interfaces. C code, can be compiled by C++ compiler, so OS4.1 does not need to support C compiler anymore. with over loaded methods, you do not need type argument, type and data argument, it already defined in the language standard. No need to interpret tag list, or var args to see what they contain. var args and tag list will ways be slow, because they are in a array, or on stack. technical overloaded methods also are on stack, but type is known beforehand, sure it’s less flexible as you need to extend number of methods, to cope with different arguments.
Edited by LiveForIt on 2024/5/15 20:47:29
Edited by LiveForIt on 2024/5/16 12:25:25
Edited by LiveForIt on 2024/5/16 12:26:05
Edited by LiveForIt on 2024/5/16 12:26:44
Edited by LiveForIt on 2024/5/16 12:28:35
Edited by LiveForIt on 2024/5/16 12:49:24
|
|
(NutsAboutAmiga)
Basilisk II for AmigaOS4
AmigaInputAnywhere
Excalibur
and other tools and apps.
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/15 19:51
#91
|
Quite a regular
|
@Hypex Quote: Hypex wrote:@MamePPCA1
Yes it was after loading modules.
What happens if you let it boot normally off HDD? Does that break as well I expect? Or partially boot from HDD?
If there is no sign of your DH0 it may be destroyed. But it would take more than file corruption. You would have needed to purposely delete the partition or reinstall RDB by installing HDD again from Media Toolbox and resetting the RDB.
Does the HDD show up in Media Toolbox still?
I recommend running Partition Wizard from Utilities. It should be installed on your pen drive.
The X5000 CD would be the only one compatible but I don't know what would stop it booting. In any case you have the pen drive that works and would be faster.
Epsilon is an Amiga fan that runs a blog. He also has an X1000, X5000 and A1222. He's experienced with X5000 and has overcome problems when messing up files. However he isn't a forum regular here.
https://www.epsilonsworld.com/search?q=x5000 OK the aparition of Early Startup Menu was after the loading of the modules. As I told before my AmigaOne X5000 resets after the splash screen.You can read it probably on my first posts. How can I install RDB? And as I said before my HDD partitions shows on Media toolBox.3 in total. Partition Wizard doesn't run.I tried before and no luck. Before I read Epsilon's blog: Has he similar HD problems as I? I want to know before read Yeah the pendrive runs faster than the CD.That's for sure.
|
|
Amiga 500 1MB Chip RAM with ACA 500+ACA1232,CD32,Amiga 1300 030/50 Mhz,32MB (now on my hands at least)and Amiga One G3 XE PPC 800 Mhz,ATI Radeon 9250 128 MB,256 MB RAM,Seagate 200 GB HD,2 working DVD drives,X-Arcade double for MAME,Sil0680,4 USB ports,LG
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/15 19:50
#92
|
Quite a regular
|
@Hypex Quote: Hypex wrote:@MamePPCA1
Yes it was after loading modules.
What happens if you let it boot normally off HDD? Does that break as well I expect? Or partially boot from HDD?
If there is no sign of your DH0 it may be destroyed. But it would take more than file corruption. You would have needed to purposely delete the partition or reinstall RDB by installing HDD again from Media Toolbox and resetting the RDB.
Does the HDD show up in Media Toolbox still?
I recommend running Partition Wizard from Utilities. It should be installed on your pen drive.
The X5000 CD would be the only one compatible but I don't know what would stop it booting. In any case you have the pen drive that works and would be faster.
Epsilon is an Amiga fan that runs a blog. He also has an X1000, X5000 and A1222. He's experienced with X5000 and has overcome problems when messing up files. However he isn't a forum regular here.
https://www.epsilonsworld.com/search?q=x5000 OK the aparition of Early Startup Menu was after the loading of the modules. As I told before my AmigaOne X5000 resets after the splash screen.You can read it probably on my first posts. How can I install RDB? And as I said before my HDD partitions shows on Media toolBox.3 in total. Partition Wizard doesn't run.I tried before and no luck. Before I read Epsilon's blog: Has he similar HD problems as I? I want to know before read Yeah the pendrive runs faster than teh CD.That's for sure.
|
|
Amiga 500 1MB Chip RAM with ACA 500+ACA1232,CD32,Amiga 1300 030/50 Mhz,32MB (now on my hands at least)and Amiga One G3 XE PPC 800 Mhz,ATI Radeon 9250 128 MB,256 MB RAM,Seagate 200 GB HD,2 working DVD drives,X-Arcade double for MAME,Sil0680,4 USB ports,LG
|
|
|
|
Re: A1222Plus has a new home
|
Posted on: 5/15 19:50
#93
|
Just popping in
|
@MaijestroQuote: Maijestro wrote:Does the sound come via HDMI or do I have to use the sound card directly? Just weighing in here. Although the A1222 doesn't have sound coming over the HDMI, there are devices called HDMI audio inserters/embedders which allow you to add audio to the HDMI signal so you could have the A1222's audio output going via HDMI. I've actually just ordered such a device myself, so I'll let you know how it goes. Kind regards, Francis
|
|
|
|
|
|
Re: A1222+ issue with CD/DVD drives?
|
Posted on: 5/15 19:05
#94
|
Just popping in
|
@MaijestroQuote: Maijestro wrote:The DVD/RW drive I want to use is very simple and requires very little power V5 with 1.6A it also has no external power source to connect. That's very similar to one of the drives I have (Hitachi-LG GP96YB70) which is the same power rating of 5V @ 1.6A. The A1222 recognised it okay and could even read from the disc, but it was unreliable using the onboard USB header as it would lose connection due to the drive drawing too much power. This was with a standard USB cable though, I don't have any of the twin USB cables to try. I also have a Plextor drive with an external power supply, which is what I was initially using to install and copy stuff from. I did negate the power issue by using a powered USB hub (an NZXT internal USB hub 3, part no. AC-IUSBH-M3-4). Both my internal Samsung DVD drive (with a USB to SATA adapter) and external Hitachi-LG DVD drive both work fine using this hub. Kind regards, Francis
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 5/15 18:22
#95
|
Not too shy to talk
|
@MamePPCA1 Yes it was after loading modules. What happens if you let it boot normally off HDD? Does that break as well I expect? Or partially boot from HDD? If there is no sign of your DH0 it may be destroyed. But it would take more than file corruption. You would have needed to purposely delete the partition or reinstall RDB by installing HDD again from Media Toolbox and resetting the RDB. Does the HDD show up in Media Toolbox still? I recommend running Partition Wizard from Utilities. It should be installed on your pen drive. The X5000 CD would be the only one compatible but I don't know what would stop it booting. In any case you have the pen drive that works and would be faster. Epsilon is an Amiga fan that runs a blog. He also has an X1000, X5000 and A1222. He's experienced with X5000 and has overcome problems when messing up files. However he isn't a forum regular here. https://www.epsilonsworld.com/search?q=x5000
|
|
|
|
|
|
Re: Hello!
|
Posted on: 5/15 17:45
#96
|
Quite a regular
|
Welcome to Amigans!
|
|
|
|
|
|
Re: Hello from Poland
|
Posted on: 5/15 17:44
#97
|
Quite a regular
|
Welcome!
|
|
|
|
|
|
Re: A1222Plus has a new home
|
Posted on: 5/15 17:42
#98
|
Quite a regular
|
Congratulations on the A1222+, Maijestro!
|
|
|
|
|
|
Re: AmiStore problems
|
Posted on: 5/15 17:40
#99
|
Quite a regular
|
Hi there, I've had the same problem. The solution was to click on the "X" next to "Code" at the top when you are viewing the shopping bag. Both invisible and visible items will then be removed. You can then add the item you want and check out. Hope this helps.
|
|
|
|
|
|
Re: A1222Plus has a new home
|
Posted on: 5/15 17:23
#100
|
Quite a regular
|
@ktadd Quote: ktadd wrote:@Maijestro
Quote:I refer again to the picture above in the post where you can see the connections of the Samsung TV.
Yes, I have a Samsung TV with the same connections. Ok thanks for the information, I'm a bit out of the loop when it comes to hardware. But since they have the same connections it should work. I also bought the analog to digital converter to be able to use my soundbar/TV system, which no longer has any analog connections.
|
|
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga 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
