Who's Online |
59 user(s) are online ( 42 user(s) are browsing Forums)
Members: 0
Guests: 59
more...
|
|
Headlines |
-
gifanimdt.lha - datatype/anim
Sep 22, 2023
-
giflib-extras.lha - development/library/graphics
Sep 22, 2023
-
dtconvert.lha - utility/filetool
Sep 22, 2023
-
libx264.lha - development/library/misc
Sep 20, 2023
-
amissl-sdk.lha - development/misc
Sep 20, 2023
-
mce.lha - game/utility
Sep 20, 2023
-
amissl.lha - library/misc
Sep 20, 2023
-
mediathek.lha - network/misc
Sep 19, 2023
-
libwebp.lha - development/library/graphics
Sep 17, 2023
-
reminiscence.lha - game/adventure
Sep 17, 2023
|
|
|
|
Re: AmigaOS 4 does not boot anymore after installing the RadeonHD V5 driver
|
|
Just can't stay away 
|
@MartinW Quote: @Tuvok
Quote:Wouldn't it be possible to have a second directory named "Kickstart2" with all the relevant modules and at boot time load all the modules from this second directory, by having a second configuration in the kicklayout file? That's what Hans just described. Yes, except that Hans suggested putting the extra configuration into a subdirectory inside the main Kickstart directory. And I agree about that, I've also been doing that in many cases (and I probably have the record in number of different boot configs, being a long time OS4 beta tester - on my X1000, the AmigaBoot menu currently goes up to the letter N  ). IMHO, it is easier to maintain and keep tidy by keeping it all inside the main Kickstart hierarchy. Best regards, Niels
|
|
|
|
Re: AmigaOS 4 does not boot anymore after installing the RadeonHD V5 driver
|
|
Just can't stay away 
|
The best safety is to create a separate boot partition, keeping both updated, but in such a way that you always update one first, check if it still boots, and if not, boot the other one and remove your updates from the first one.
Only if the newly updated system does boot and work, should the second (fallback) partition also be updated.
Best regards,
Niels
|
|
|
|
Re: Amiga books: from Vultures to VAMPIRES video review with Trevors introduction
|
|
Just can't stay away 
|
@kas1e Quote: David says that he sent Volume 3 to the printers, and he has just been advised they should take delivery in September. Sounds perfect - I'm hoping to buy volumes 2 and 3 (with personal dedications) at Amiga38 in Mönchengladbach in October  . I bought the first volume there last year. Best regards, Niels
|
|
|
|
Re: tbimages: missing - how to get to them?
|
|
Just can't stay away 
|
@Reth
The standard User-Startup has this line (after the MUI stuff):
assign tbimages: SYS:Prefs/Presets/tbimages
Is that missing in yours?
Best regards,
Niels
|
|
|
|
Re: Introducing the Rear Window blog
|
|
Just can't stay away 
|
@trixie I agree with others here, don't let his view on things weigh you down. It sounds like he has been so busy making a living and a life for himself doing whatever he was (self-?)educated to do, that he never really got time to find out how to enjoy "playing" and experimenting, either with the tools of his daily work or for that matter some completely different hobby. It's something that I have seen happen to some people who make computers and programming their carreer. Maybe in the beginning it fascinates you enough that it can fill not only your working hours, but also your spare time. And then the road to total nerddom is paved and polished. Then again, databases *are* fascinating ... I spent the last couple of decades of my career getting deeper and deeper into them  . But I was lucky enough to have a life as well - and my Amiga interest. Thanks for an excellent post with lots of food for thought. Best regards, Niels
|
|
|
|
Re: Radeon RX cards on X1000
|
|
Just can't stay away 
|
@Tuvok Quote: Are you one of the responsible persons for the wiki? No, I haven't had anything to do with that, only beta testing and translation (and the Workbench.guide long ago). There were a few people who worked on the Wiki at some point, but I don't remember exactly who. Best regards, Niels
|
|
|
|
Re: Radeon RX cards on X1000
|
|
Just can't stay away 
|
@Tuvok Quote: (ATI R9250) CMPLENGTH=19 Boardname=Radeon RX Polaris 12
(AMD RADEON RX550) CMPLENGHT=11 BOARDNAME=Radeon 9250
(AMD RX560) CMPLENGHT=19 BOARDNAME=Radeon RX Polaris 11
(Gigabyte R9 270X) CMPLENGHT=15 BOARDNAME=Radeon HD Oland
(Sapphire HD 7970) CMPLENGHT=21 BOARDTYPE=Radeon HD 7900 Series
It seems strange that you use the boardname "Radeon RX Polaris 12" for your ATI R9250, and the boardname "Radeon 9250" for your AMD RADEON RX550), but maybe that was just a typo when entering the info here? But maybe more important: You have CMPLENGTH=19 for both of the boardnames "Radeon RX Polaris 12" and "Radeon RX Polaris 11". Those names are 20 characters long each. So in effect you have created two monitor files which will be seen as one and the same, i.e. a random one will be picked, because the CMPLENGTH tells the distinguishing code to only compare as far as the 19th character, which means you have two monitors with the name "Radeon RX Polaris 1" (the "1" or "2" at the end are not seen in the comparison. At least that's how I have understood it. Best regards, Niels
|
|
|
|
Re: qemu emualtion of AmigaONE XE
|
|
Just can't stay away 
|
@joerg Quote: untested, but saving it as board.c and using "execute board.c" in a shell should work It does - once you get all the 0xA0 characters (from the copy/paste out of the code field) replaced by normal spaces  . Best regards, Niels
|
|
|
|
Re: AmigaOs4.1 how much memory is used.
|
|
Just can't stay away 
|
@Maijestro
It will also depend on your screenmode - resolution as well as depth.
Hint: You can make your Workbench always tell you what is currently used, among other things. Check out the Workbench prefs editor.
I use the following string (almost, this is translated from Danish and simplified a bit) in the screen title format:
AmigaOS %r (ver: %v/%vw) on a %c with %mtj GB memory (%mj GB unused) and a %g with %mgtm MB (%mgm MB unused)
Best regards,
Niels
|
|
|
|
Re: Is this a glitch or is it normal?
|
|
Just can't stay away 
|
@msteed Quote: Having spent a lot of time getting the look I want, and getting Reaction and MUI synchronized so everything looks consistent, I'm not inclined to change any of the settings now. You might consider making backups of the relevant .prefs files in ENVARC:Sys/ - or if you're lazy, simply backup the whole directory. That way you have a quick and safe way to get back to your current settings, so you don't have to be afraid of experimenting. BTW, what about the font you're using for the title bar, has that been changed? Just an idea. Best regards, Niels
|
|
|
|
Re: AmiUpdate and newlib.library....
|
Posted on: 6/27 23:04
#11
|
Just can't stay away 
|
@Maijestro
It looks from your log like there was a problem with Rigo's codebench server or its network connection at the time you tried.
I just did a search with AmiUpdate, and it connected fine now, so try again.
Best regards,
Niels
|
|
|
|
Re: AmiUpdate and newlib.library....
|
Posted on: 6/23 23:16
#12
|
Just can't stay away 
|
@Chris Quote: You need to manually edit/create the authentication file. There's a bug in Amiupdate which stops it creating the file. I'll have to have a look to see what it is called. The name is SiteList, and it is found in the main directory of AmiUpdate. Best regards, Niels
|
|
|
|
Re: Daylight saving settings not saving properly in Time Prefs
|
Posted on: 6/20 22:02
#13
|
Just can't stay away 
|
@VooDoo Quote: I tried already but no luck. I wrote that command in shell after I set up clock in Time Prefs. Maybe I am doing something wrong? Well, after "setclock reset" the current time needs to be saved into the batterybacked clock. So after the reset, set the system time (using the date command or your Time prefs), then do a "setclock save". But if that doesn't help, then your problem must be a different one. Best regards, Niels
|
|
|
|
Re: Daylight saving settings not saving properly in Time Prefs
|
Posted on: 6/19 23:23
#14
|
Just can't stay away 
|
@VooDoo
As salass00 suggests above, try "setclock reset". Your description also sounds to me like that could help.
Best regards,
Niels
|
|
|
|
Re: Redirect STDERR and STDOUT to the same file
|
Posted on: 6/12 22:39
#15
|
Just can't stay away 
|
@rjd324 Quote: Perhaps you cannot reproduce it because you are not using the Enhancer version 54.5. That's correct, I don't. Well, you know where to go with that one, then. Edit: Ah, I see Costas is already on it  . Best regards, Niels
|
|
|
|
Re: Redirect STDERR and STDOUT to the same file
|
Posted on: 6/11 23:46
#16
|
Just can't stay away 
|
@rjd324 I can't reproduce your truncation:
Ny Shell-proces, nr. 22
22.WB-F: 0 0 [0,000.396] Mandag 12/06-2023 00:36:10
$ delete RAM:p
22.WB-F: 0 0 [0,000.585] Mandag 12/06-2023 00:36:20
$ dir xx >> RAM:p *>> RAM:p
22.WB-F: 20 205 [0,000.646] Mandag 12/06-2023 00:36:30
$ type RAM:p
DIR: Kunne ikke finde oplysninger om "xx".
DIR: objektet findes ikke
22.WB-F: 0 0 [0,001.372] Mandag 12/06-2023 00:36:36
$
Quote: Why append? This is not what I would have expected. Perhaps because if you don't append, but just write, the first redirection (the STDOUT) locks the file so the second one (STDERR) can't write to it. And maybe they both try to verify that they can get their locks before either one starts to actually open (create) the file, because it seems to fail without even creating the file. And that probably also means it wouldn't help using append only for one of them. But I'm guessing. Best regards, Niels
|
|
|
|
Re: Redirect STDERR and STDOUT to the same file
|
Posted on: 6/11 22:26
#17
|
Just can't stay away 
|
@rjd324
Have you tried this?
dir xx >> RAM:p *>> RAM:p
Works for me.
Best regards,
Niels
|
|
|
|
Re: What is the current situation with printing in OS4 on real hardware?
|
|
Just can't stay away 
|
@eliyahu
In the standard AmigaOS4.x installation of Ghostscript there is a script in SYS:Utilities/Ghostscript/Data/8.54/lib/ called ps2pdf.
I have no idea whether is can run under AmigaOS (it does look like it's part of something copied directly from the Linux GhostScript). It will at least require the sh shell, but if you have the SDK installed, it should be available.
Worth a try, at least as a starting point.
Best regards,
Niels
|
|
|
|
Re: MorphOS 3.18 is out
|
Posted on: 5/16 23:43
#19
|
Just can't stay away 
|
@geennaam Quote: Afaik, only 4.0 and 4.1 were paid releases. Well, also 4.1 Final Edition (4.1 FE) was a paid release. But the updates to that - Update 1, Update 2 (with HotFix) and a few later released single-module fixes - have all been free for registered users of 4.1 FE. Best regards, Niels
|
|
|
|
Re: MorphOS 3.18 is out
|
Posted on: 5/15 22:19
#20
|
Just can't stay away 
|
I must say I don't see how a simple announcement of a new MorphOS release is a problem here (although it would of course have been even better to have it in Free for all).
The only problem with it is when it is turned into a discussion about whether it should be here or not. (Oops, now I did it myself ...)
Best regards,
Niels
|
|
|
|