Be careful of spelling with the boot args: it should be noioapic rather than noioacpi. You can check if the IO-APIC is in use by looking at IRQ numbers in PCITool: if in use, high IRQ numbers will be seen like 18, 19, 20 etc.

Please try the 1024 test with noacpi, and with noioapic if you think it may have been misspelled on the initial test. If 1024 kills the connection (can't do a normal ping afterwards), the system (PC+OS) is unstable overall.

Spelling was never my strong point...

I've tried the tests again with the spelling correct ( ) with nothing, noacpi and noioapic - same result as above in quickly going to no buffer space. In fact slightly worse than yesterday, it was just 6 to 7 seconds for each test before being out of buffer. The stack is not taken down, I can ping again after the test and indeed launch OWB to type this.

Cheers,
Nigel.

The buffer space errors might be a red herring then, as it's not too serious if it doesn't take the stack down (in other circumstances, those errors are often associated with driver bugs that bring networking to a halt).

So maybe you should just continue browsing with noioapic to see over time if it seems as good as noacpi. But if you want to try another ping test, I'd suggest leaving out the "-s 1024" option and see if the flood ping keeps going for say 30 minutes (if you still get buffer errors, note them but let the process continue). Then Ctrl-C it after 30 minutes and check if normal pings still work.

OK I'll give that a try, but I realised today I'll need to use noacpi. I've decided to move over to my 64 bit machine for work, and I need to be able to connect it to external displays which is only possibly with noacpi as this allows me to use the screen switch button.

Talking of work, could I please ask for some advice on a recent issue? About a month ago I stopped being able to access websites in work on my 32 bit machine. According to the output from WirelessManager there is an authenticated connection to the netork, but for any website I try in OWB I get a timeout before the website is opened i.e. nothing is transferred at all. It looks like the DNS server is not being reached. Everthing was fine before about a month ago and I found today it's the same for 64 bit. IP address and DHCP are set to auto and everything is fine on my home network.

Any insights would be much appreciated. Of course, it could be a M$ update designed to make things even more difficult for users of alternative operating systems...

Cheers,
Nigel.

For the problem in work, I'd recommend running some diagnostic commands.

First, to check if you're getting an IP address from DHCP: ifconfig net0

And for DNS (assuming pings aren't blocked on the network): ping google.com

Or try this in Odyssey: https://192.245.1... (if you get a page that says "Sorry", it's working correctly)

Thanks for the information on the tests. Results are:

ifconfig - an ip is being assigned

ping google.com - 100% packet loss

In OWB 192... etc - page not loaded, timed out.

Cheers,
Nigel.

Hmm, do you think a proxy is required? Do you have a PC with a mainstream OS on that network to compare with?

Does ping find the IP address for google.com?

I assume you have "Automatic" mode enabled globally as well as for the interface in Network prefs?

This is on the guest network used by other staff and students, there are no issues accessing it through mainstrean OSs including Android and iOS.

Yes, automatic is set globally.

Cheers,
Nigel.

Maybe try to find out if other OSes are using a proxy. It might be shown in the settings for the wireless network you're on, or you could try a site like this that apparently detects whether you're using a proxy: https://www.showm...oxy-check/

According to that site, not proxy.

I'm at the Midlands Amiga Enthusiasts meet again tomorrow to show 64 bot AROS, so I'll see how well the wifi works there.

Cheers,
Nigel.

No issue getting onlune and browsing at the meet today; looks like something 0my college has done...

Cheers,
Nigel.

So I finally decided to raise this issue with my college IT department and they are asking for the address of the DNS server my machine is trying to connect to; is there any way to find this on AROS?

Cheers,
Nigel.

You can start networking with manual addresses, then run dhclient in the console. That should show you the details negotiated through DHCP.

Many thanks - I'll try that tomorrow at work.

Cheers,
Nigel.

I contacted my college's IT department about the above issue. They confirmed my machine was authenticting on the network but couldn't see why the login page was not bein sent to my machine (about once a month a page pops up asking for a username and password). It seems the Cisco system we are using is very much a 'closed box' and so the IT technicans cannot see exactly why it's failing. This isn't an issue with the new 64 bit builds as it first happened on my 32 bit machine which previously showed the login page fine, so it must be domething to do with a server update. Hopefully the issue will not become more widespread.

Cheers,
Nigel.

Well, the offidocs service provides many applications from the open world

Dos anyone get the error with Amazon attached and does anyone jow how to solve it? I can load the Amazon homepage but every search I do ends up with the page attached. I've tried all the different spoofing options, clearing cookies and updating ca-bundle.crt to no avail. I've had this issues for quite some time but it's intermittent - sometimes Amazon works fine, and other times this happens.

For context, aside from pullng up ArosWorld as my homepage, Amazon is the first site navigated to and running OWB straight after a reboot does not help. I also get exactly the same problem on 32 bit.

Cheers,
Nigel.

A few months ago Blender and GIMP also worked, now only the Office suite maybe it works on owb 3.0 I am currently using OWB 2.0

Reproduceable error (please see attached). This is on nfas.net/join-renew; the crash happens when you try to select the year from the drop-down in the date of birth field.

Cheers,
Nigel.

Thanks for reporting this. I'm currently working on another topic but when I get back to refreshing Odyssey to newer enginer version, I'll take care of those bugs.