Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
36 user(s) are online (27 user(s) are browsing Forums)

Members: 1
Guests: 35

daveyw, more...

Headlines

Forum Index


Board index » All Posts (BillE)




Re: PM email notification
Quite a regular
Quite a regular


@Raziel


Your little anim GIF worked well, hopefully you will see the same for the PM I have sent to you

Go to top


Re: PM email notification
Quite a regular
Quite a regular


@Raziel


I'll second that.

I don't get many PMs so don't think to check for them every day.

When I do, it certainly isn't obvious and it can be a good few weeks before I see I have had a PM on this site.

Is there any way to tell you that there is a waiting PM without having to click on the User Menu ? Having it hidden in a menu item you tend to not even look at is not really ideal.

Go to top


Re: OS4.1 native find-tool
Quite a regular
Quite a regular


Thanks for the useful tips, great stuff.


@nbacheQuote:

Hmm, just tried that here, it doesn't seem to do what you describe.
Niels


Click out of the Pattern string container first!



Bill.

Go to top


Re: New AmigaOS 4.1 SDK 53.34
Quite a regular
Quite a regular


@walkeroQuote:
walkero wrote:
@BillE

If you get one of the example sources, i.e. the examples/GUI/window/window.c and copy that to ram, and then you compile it, then you get that error?

I tested locally the following and work fine:

RAM Disk:> gcc -o Window Window.c -lauto
AmigaOSbeta:> gcc -o ram:Window ram:Window.c -lauto
AmigaOSbeta:> gcc -o "RAM Disk:Window" "RAM Disk:Window.c" -lauto


Interestingly, the last two methods work fine. So it seems as long as the shell is not set to the RAM: directory compiling from ram: using full paths works from other directories.

Weird.

This seems to be narrowing down my problem to running the shell with RAM: as its default.

I am still set to 53.30 but will go back to 53.34 as I am now sure that the version of the SDK is not the problem, I only noticed it after upgrading.

Go to top


Re: New AmigaOS 4.1 SDK 53.34
Quite a regular
Quite a regular


@walkero

Interestingly, if I create a RAD: disk I have no issues compiling from that device. It seems only RAM: that is affected.

Go to top


Re: New AmigaOS 4.1 SDK 53.34
Quite a regular
Quite a regular


@walkeroQuote:

Maybe a good test would be to make a new installation of 53.30 and test it again, and see if you get the same issue with that.


No need to reinstall it, it was already there in a directory called old_sdk, so all I needed do was rename the folders to sdk_new and sdk and reboot.

The new install of v53.34 was a red herring, I still get the same problem when compiling from ram:. It seems OK if compiling from an HD partition. I had not used the SDK recently until installing the new one so it looks as if the problem was already there. Maybe something has changed in the ram handler that GCC does not like ?

The space in the name "RAM Disk" does not seem to be it, I renamed it to one word before trying a compile and still get the same error if compiling from Ram: (RAMDisk:).

I am using a fairly pristine OS4.1FE update 2 with Enhancer 2.2, but without some of the command replacements. I'll try some older boot partitions to see if they make any difference.

Go to top


Re: New AmigaOS 4.1 SDK 53.34
Quite a regular
Quite a regular


@walkero

Quote:

Do you get that error even if you compile a Hello World example?

Do you have AmiCygnix installed on your system? If you do, you have to make sure the SDK assigns are done before the AmiCygnix.


It seems to haopen with any .c file no matter how simple.

I don't have AmiCygnix so that can be ruled out as a cause.

Go to top


Re: New AmigaOS 4.1 SDK 53.34
Quite a regular
Quite a regular


@smf

Quote:
smf wrote:
For one user the message could appear random when using the amiga shell (no error message when using the sh shell)

For another one it could happen when compiling sources from the ram disk:


We may be getting somewhere.

I always do compile from files copied to the ram: disk. It avoids overwriting things by accident. However, doing it that way always worked in the past, it is just with the newest SDK I get a problem.

SH, I am not really sure what this is and why I would use it in place of the Amiga console ? OK I tried typing sh into a 'real' concole and got an interface with a \

It did not like me typing ram: to get to the required directory so I now do that first and then enter sh.

Now I do get some normal output when running gcc ro make. As I expected it was full of errors as my SDK as yet has no third party includes, it is still pristine. So anything needing those includes gives an error - no problem that can be fixed.

The thing is why would I need to use SH, I never had to before. Just doing everything from the normal shell worked fine.

Go to top


New AmigaOS 4.1 SDK 53.34
Quite a regular
Quite a regular


I downloaded this a while ago. As my SDK over the years had become a bit of a mess with additions and beta files I thought it would be best to get something that should work straight out of the box with the latest OS4 update 2.

However evertime I try to compile somethying I get the following message:

assertion "cached == 0" failed: file "../../gcc/libcpp/line-map.c", line 277
cc1: internal compiler error: Aborted


Any ideas as to what this is and how I get rid of it.

Does anyone else get this weird message. Surely as it was downloaded straight from the Hyperion site it should work without any need for alterations ?

Nothing has been added from my older SDK this is a brand new install.

Go to top


CloudFlare
Quite a regular
Quite a regular


Hi,

More and more when I click on a link to a site instead of actually going to that site I get a page apparently hosted by something called CloudFlare which is "checking my browser" sometimes bothers to give me a Captcha which seems to work but then the whole thing just loops around to the checking your browser status.

Resized Image


RIGHT CLICK OPEN IMAGE IN NEW TAB OR WINDOW FOR FULL SIZE.


I ask whether it is Odyssey or the problem is just specific to me because I have not seen any other mention of it on Amigaworld nor Amigans. This specific screengrab is from a link on Amigans for Walkero's Odyssey Scripts thread. Now given that the subject was Scripts for Odyssey one would guess that most will visit that page using Odyssey but no-one other than myself has ever mentioned cloudflare on Amigans. Even if people then resorted to using another browser on another system you would still think there would be mention of it ?

Is there a way to just get directly to the site you want and bypass this cloudflare crap totally ? Would one of Walkero's useful scripts help?

Are there any specific spoofing requirements needed or any other Odyssey settings. I really wish to not see cloudflare any more !



Bill.

Go to top


Re: Odyssey Search Engines Order
Quite a regular
Quite a regular


@levellord

I think I just edited the file Odyssey/conf/searchengine.prefs

I don't think you can do it within Odyssey itself - an oversight I guess.

Go to top


Re: AmigaOS 4 Monthly Roundup - February 2022
Quite a regular
Quite a regular


@nbache

Quote:

I can say that for me it works fine in Odyssey (latest 1.23 r5 from jan 2 2022) on X1000.
So maybe your idea about an ad blocker or something is worth a closer look?

Best regards,
Niels


Exactly the same Odyssey and hardware setup here. Unfortunately still no joy with the adblock disabled. Even though I do have other options I would like to solve the mystery. Maybe the curl file ? I have the version dated 1/1/22 size 208065 which seems pretty upto date.

ANyway I have had a quick scan of both the Jan and Feb issues and am impressed. There seems more info there than in any of the forums or magazines. Maybe not the former but its all in one place.



Bill.

Go to top


Re: AmigaOS 4 Monthly Roundup - February 2022
Quite a regular
Quite a regular


@AmigaOldskooler



Hi, This is really weird. I just tried on my Amazon Fire HD with Silk, and it worked ! The site is OK with Netsurf on my X1000. Works on Chrome on Fire HD too.

Just not Odyssey on X1000 nor IE and Chrome on PC at work. The work PC may be blocking the site probably because of the word "gaming" but the message was not the usual one for that case, I'll check again next time I am in.

I can also see what happens on a MacBook Pro once I recharge it, and can also try an iPhone (I'll need to find a magnifying glass to use that!).

I can read the Roundup anyway now.

Why some work, some don't is a mystery.

Maybe I have something in Odyssey's ad blocker that is causing the problem ?

Go to top


Re: AmigaOS 4 Monthly Roundup - February 2022
Quite a regular
Quite a regular


@AmigaOldskooler


This link is not working at all for me. I tried yesterday at work on a PC too using both Chrome and IE. They seemed to indicate out of date TLS or something like that. So for once it appears not to be an Odyssey only problem.

At home using Odyssey, I get the following:

Resized Image



Any ideas as to why everyone in the world can access this link but I can't. Work and home do not use the same providers so I do not think it is a provider issue either.

It is not just that specific URL anything at amigaos4gaming.com has the same issue.

Go to top


Re: SonosController - looking for beta testers
Quite a regular
Quite a regular


Will it work with Amazon Echo smart speakers ?

Go to top


Re: A new editor for AmigaOS 4 is in the works
Quite a regular
Quite a regular


@walkero


How do you get past the cloudflare crap ?

Go to top


Re: Old/new user from Austria
Quite a regular
Quite a regular


@Raziel

Quote:
Oh...how did i end up with "America"?

Must be the "Last Unicorn" spooking around in my head


Either its that unicorn or more likely a horse with no name

Go to top


Re: aiostreams new release
Quite a regular
Quite a regular


@walkero


The site does not work in Odyssey. It is this Cloudflare nonesense which discriminates against browsers it does not khow about. All you get is a Captcha that you cannot get past, the same page just keeps loading. Can you please give Amiga friendly links !

Go to top


Re: aiostreams new release
Quite a regular
Quite a regular


@walkero


The site does not work in Odyssey. It is this Cloudflare nonesense which discriminates against browsers it does not khow about. All you get is a Captcha that you cannot get past, the same page just keeps loading. Can you plese give Amiga friendly links !

Go to top


Re: NG Amiga user questionnaire
Quite a regular
Quite a regular


@jap

Interesting but may be skewed as people that use OS4 for everything such as myself could not take part in a poll that will not run on Amiga browsers. Next time meake sure you test it out with Odyssey first.

No point really in having polls Amiga users cannot access.

Go to top



TopTop
(1) 2 3 4 ... 27 »




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project