Hello

I'm having a problem for a while here and wanted to know if some others here are experiencing the same problems.
And if they would have a solution for it.

The problem is that whenever i try to load AW.net on AWeb PPC (3.5.05)
it often hangs when i try to scroll the slider down, and it seems to happen when the site is not fully loaded yet. i just found out it also can happen when i click into the space to type a password to login.
then a GR pops up and starts to complain about an error of DSI and some other stuff i cannot remember, i might make a screenshot of it for ppl who want to see it later.

I'm having a µ-A1-C with 256MB RAM, OS4 upd. 3 and the latest UBOOT.
I also tried to take any un-necessary stuff out of WBStartup so that the system runs as standard as possible.
I also did run snoopdos, but cant find missing stuff

The problem also occurs on a few other sites i visit regularly. but not too frequent on those ones.
an example of those sites i can remember is www.fastmail.fm my webbased emailservice.

Another thing is, that i always need to use IBrowse when i want to login to write posts. thats also not working on AWeb PPC. i think that this is a bit strange for a site which supports A1/OS4 and their thing doesnt work properly on such a system !

Hopefully i gave enough information, if not, pls tell me what to do to give more info.

greetings.

@kokkie

I'm having it worse than you now and then. I'm using the unofficial version
3.5.06, and it causes such crashes a little more often than you might discover.

I suggest that every time you get a GR, then write out a crashlog to RAM and
copy it to a Doc-drawer, then email it directly to the editor of AWeb..

Later versions should be more bug-free and hopefully have more supports for
stuffs that we have been waiting long for

In overall, AWeb really is excellent, except to these bugs of course

@Helgis

you're saying:
I'm having it worse than you now and then. I'm using the unofficial version
3.5.06, and it causes such crashes a little more often than you might discover.

I have tried that version also with same results happening.
but you think it doesnt happen too much for me no ? ;)
Well it happens approx. 6 times a day, when browsing AW.net
I sure can wait for it to crash.
Nice thing is, that sometimes i can close the prog and restart it again, without having to reboot first !

you also said:
I suggest that every time you get a GR, then write out a crashlog to RAM and
copy it to a Doc-drawer.

Pls tell me how to do that.

greetz /me

@kokkie

Hi,

If your problem is "logging in" at AW with AWeb, please check your settings in
"Aweb network settings/5 Privacy". You should have "Suppress Referer while browsing"
UNchecked. You should also have "Use cookies" set to "Always (quiet)".

In regard to your other problem, please wait for upcoming release of AWeb version
3.5.07.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Helgis

Quote:..."write out a crashlog to RAM and copy it to a Doc-drawer, then email it
directly to the editor of AWeb."

Excellent idea. A step-by-step that produces an error (if possible) along with a
crash log is very helpful for authors in debugging their applications.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Thx for your help, gonna try that out now ! :)

greetz

@kokkie

As regards writing a crashlog: WARNING: Any change you make to startup-sequence
you make at your own risk. That being said...

The first line of update3 startup-sequence is a commented line regarding version.
The second line of update3 startup-sequence is "C:SetPatch QUIET".

Add these lines BETWEEN the first and second lines:

kdebug "debuglevel 0" >NIL:
kdebug "console memory" >NIL:

Save your new startup-sequence.
Now, when you get a "grim reaper"...
(1)Open the Shell
(2)Type: DumpDebugBuffer >RAM:error.debug
(3)You may then open a disk utility like Diskmaster and rename the file you
just saved to something more recognizable if you wish.
(4)Copy this file, as @Helgis suggests to a directory where you keep your crash logs.
(5)When you email a developer describing as best you can a step-by-step that
created your crash, also include as an attachment the corresponding crash log
file you just saved.

Note:I have done this for months without problems and devs appreciate it.
The added benefit on A1-C is that serial debug will no longer interfere with
standalone modem use, since debug is re-directed from serial port (0) to console.

Questions?

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@kokkie

Regarding "login" at AW, also please read:

http://amigaworld.net/modules/faq/index.php?cat_id=1
Relevant question:Why Can't I Log In?

Note:The option to "suppress referrer header" can remain checked for most all
web sites, just not here.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Helgis

I can agree whit that, I'm sorry to say that crashes I get I normally don't send the developers any thing, I'm just hope some one else is going too

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Well, there is certainly a difference between a "grim" (where you can still
function) and a true hard crash.
In the case of the hard crash, my method will, of course, be of NO use.

@thread

Please keep in mind the following article by @Wegster available here on OS4Zone,
concerning the same subject of serial debug:
http://amigaworld.net/modules/features/index.php?op=r&cat_id=4&rev_id=125


Best Wishes,
#6

Last edited by number6 on 01-Oct-2005 at 01:50 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Well you're talking about a setting called "Suppress Referer while browsing"

Now i need to know which one that is, as i tried a few settings without success.
So i'm really wondering which setting you meant:

For your convenience i'll type over the ones i can choose from:
Beware they're in Dutch ! ;P

----
V Browse anoniem.
V Waarschuwingen voor onbeveiligd verzenden.
V Activeer 'spam'-blokkade bij posten van nieuws.
V Gebruik email-adres als FTP anoniem wachtwoord.
gebruik cookies (Altijd/Nooit/Vragen)
V RFC 2109
----


I also reply for your latest post down here,
you said:
As regards writing a crashlog: WARNING: Any change you make to startup-sequence
you make at your own risk. That being said...

So i suppose that when i precisely do what you're telling me i will not ruin my OS4 installation right ?
Or in other words, make a back-up of the startup-sequence 1st before changing it ! ;)

Then you also said:
The added benefit on A1-C is that serial debug will no longer interfere with
standalone modem use, since debug is re-directed from serial port (0) to console.

Is that when you attach a serial cable between 2 serial ports of 2 computers ?
I've read about that in some other post..

Well i can be short on this, at present i dont have another working computer here which suits that task ;)

greets

Last edited by kokkie on 01-Oct-2005 at 02:00 PM.

@kokkie

"V Browse anoniem" - UNcheck
"V RFC 2109" - UNcheck

As to my method for collecting serial debug and sending to developers:
If you feel more comfortable, wait until an OS4 developer checks in to this
thread and responds.

As to the added benefit of using this method on Micro A1-C: It will protect
anything traveling down serial port(0), which is your ONLY serial port on the
Micro. So that would also protect in the case of a serial cable attached between
two computers.

Note:If you are using @Wegster's method for collecting serial debug, the method
I have outlined would defeat the purpose. The method I descibe "redirects" serial
debug to a "safe" place. To use @Wegster's method, you would "require" serial
debug to function normally. I believe his method is most effective if you own an
A1XE, since you have two serial ports instead of one.

I use the described method because, simply, the most common problem is the appearance
of "grim reaper" windows. The method I describe will address the problems that result
in popping up that window and allow you to create a text crashlog.

A hard crash or a system lockup (also referred to here as a "freeze") can not
be debugged by the method I have outlined.

@thread

If anyone would like to report on the effectiveness of using the program
SahimiPPC as an alternative for debug output, the input would be welcome.


Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@kokkie

Re: AWeb PPC crashes on AW.net

I also have this problem. I don't know why this happens, but AWeb seems to download part of the amigaworld.net webpage, then stops for awhile before downloading the rest. The transfer anim stops rotating while AWeb waits. If you click on the "?" button below the >> button, you will see that there are still some gifs "connecting". If you move the scroll slider bar down during this waiting time, AWeb will usually grim. I usually click the double stop button (lower right hand corner in the "Network Status" window) to stop the transfer, and then I can proceed normally. Otherwise you have to wait for almost a minute for the rest of the gifs to finish.

I am also using a µA1-C with 256MB RAM, OS4 update 3 and the latest UBOOT.

--
redfox

Last edited by redfox on 02-Oct-2005 at 03:33 PM.
Last edited by redfox on 01-Oct-2005 at 03:47 PM.

@redfox

how many connection have you opened in Network Settings>Options?

Try to change it to a lower or higher value. (it rely by your ISP connection speed and TCP/IP stack)

_________________

@number6

I've been using SashimiPPC for a month or two. As a µA1 user I'm disturbed by the number of programs that write to the serial port to report things like "program started", "window opened" etc. For example, YAM PPC sends a lot of startup reports to the serial port when you start it but doesn't give you a clue as to what function caused a crash. When the system catches a problem and stops the program it reports a single line to the serial port. Sending the Grim Reaper log to the serial port doesn't give me any more information than saving the log to a file. When the system crashes, the output seems to bypass normal debugging output and writes directly to the serial port.

SashimiPPC seems to work reliably and helps keep serial debug output away from my serial port which is connected to a modem for dialup connection. I would recommend that uA1 users who are using a serial dialup-modem either install SashimiPPC or use your method to control debug output.

_________________
X1000 with 2GB memory & OS4.1FE

@kokkie and all

When you see the GR message. Click on More, and the button saying
Write Crashlog. Then it should automatic write it in RAM. Check the crashlog
in RAM. Copy it to a place where you store documents, then email the editor
of the program by sending that crashlog as an attachment, and there you go..

Yes, i'm using the unofficial version. Of course more buggy than perhaps the
other versions you're using. I'm waiting for version 3.5.07 to become official..

Last edited by Helgis on 01-Oct-2005 at 04:02 PM.

@Xenic

As always thank you for your input. I have tried SashimiPPC also. I just wanted
the opinion of some other people here. Sneaky huh?

I agree with your conclusions, particularly in regard to using one of the two
methods we have outlined in conjuncion with use of Micro A1-C and serial modem.

Note:My method is actually the method of OS4 team. Credit where credit is due.

@thread

An interesting news piece regarding the "grim reaper" here at AW:
http://amigaworld.net/modules/features/index.php?op=r&cat_id=6&rev_id=34&sort_by
(ONLY 47,568 reads?)

Best Wishes,
#6

Last edited by number6 on 01-Oct-2005 at 04:26 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@redfox
@ at those having this problem

Please try the "arrow keys" and "shift arrow" etc. combinations (instead of the
scroll bar) and report back if you still have this problem of reaching the bottom
of page before the entire page is loaded. Thanks.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Helgis

NO!
@kokkie and others have Micro A1-C. Merely pressing the "write crashlog" does
not prevent serial debug from travelling over port(0) on the Micro.
You MUST follow the instructions and/or advice given by @Xenic and OS4 team to
avoid that potential problem, particularly if operating with a device like a
serial modem connected to the serial port.
You have XE. The matter is different for owners of XE since you have two serial
ports. Understand?

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Framiga

Quote:"Try to change it to a lower or higher value. (it rely by your ISP
connection speed and TCP/IP stack)"

Good advice. Default in AWeb is, iirc 8.

Problem I have noticed, particularly through use of A1serial and dialup modem:
connecting to too many files (small ones like the many AW gifs) presents
more of a problem for the system then just connecting and downloading one large
file. Any thoughts on this?

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*