Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Amigaz on August 20, 2006, 01:03:57 PM

Title: Facts (clock synk) still crashes
Post by: Amigaz on August 20, 2006, 01:03:57 PM
After getting Genesis (AmiTCP) to start way before Facts which needs a running TCP/IP stack to function or it will crash it still crashes even though I have Genesis started early in my user-startup.
I have Facts in my WBStartup which is recommended, have tried different startup priorities without any effect and WAIT/DONOT WAIT but still crashes like on my screenshot, any clues?  :-?

EDIT: Genesis wasnt started at all as I thought, lol

so back to the "drawing board" :P
Title: Re: Facts (clock synk) still crashes
Post by: Amigaz on August 20, 2006, 02:14:57 PM
Now trying to run Facts from a script started as an online even in Genesis but the TCP/IP stack isn't started fast enough when Facts tried to access the NTP server so is there a way to add some seconds of wait in the script or make the TCP/IP stack start faster? :D

My script: Workbench:C/Facts  >RAM:TimeTrace

Error reported by TimeTrace: FACTS 5.04 by Chris Young
© 1998-2006 Unsatisfactory Software

You are currently in daylight saving time! (BST )
Your timezone is SYS (2 hrs from GMT)

Looking up host ntp.lth.se...

Error with DNS lookup
Title: Re: Facts (clock synk) still crashes
Post by: keropi on August 20, 2006, 02:18:22 PM
damn, wish I could help...
dead A4000 battery? that's why u want this prog, right?
Title: Re: Facts (clock synk) still crashes
Post by: Amigaz on August 20, 2006, 02:23:41 PM
Quote

keropi wrote:
damn, wish I could help...
dead A4000 battery? that's why u want this prog, right?


Thanks for the sympathy  :-P

Dead battery, it's an A4000 CR..the previous owner has removed the original coin battery and wired a new coin battery with two cables so the battery is hanging but insulated with electric tape I'm going to put a new battery in the original place when I'm not too lazy  :-D
Have seeing the date 1978, Januari 1 in Limpidclock each time my miggy starts  :crazy:
Title: Re: Facts (clock synk) still crashes
Post by: quenthal on August 20, 2006, 03:02:08 PM
Hmm.. normal maybe normal wait command will do fine in your script - c:wait 2 ; 2 second delay before next command?

There is newer and more configurable versions in aminet in util/
Title: Re: Facts (clock synk) still crashes
Post by: Amigaz on August 20, 2006, 04:03:27 PM
Quote

quenthal wrote:
Hmm.. normal maybe normal wait command will do fine in your script - c:wait 2 ; 2 second delay before next command?

There is newer and more configurable versions in aminet in util/


If I use "Wait 2 Workbench:C/Facts >RAM:TimeTrace"

I get this reported from TimeTrace: too many arguments

 :getmad:  :madashell:  :crazy:
Title: Re: Facts (clock synk) still crashes
Post by: Piru on August 20, 2006, 04:08:10 PM
@AMIGAZ

'Wait' is a separate command. It can't be on the same line.
Title: Re: Facts (clock synk) still crashes
Post by: Amigaz on August 20, 2006, 04:53:35 PM
Quote

Piru wrote:
@AMIGAZ

'Wait' is a separate command. It can't be on the same line.


Ahh... :idea:

So a script with two lines will do the trick?  :-P
Title: Re: Facts (clock synk) still crashes
Post by: quenthal on August 20, 2006, 05:31:44 PM
Yes, with two line script it should work.
Title: Re: Facts (clock synk) still crashes
Post by: motorollin on August 20, 2006, 05:39:47 PM
Wait 2
C:Facts >RAM:TimeTrace

--
moto
Title: Re: Facts (clock synk) still crashes
Post by: chris on August 20, 2006, 06:54:05 PM
@AMIGAZ

Try blanking out your tooltypes and reconfiguring again from scratch, if you are having problems starting it from WBStartUp.

There seems to be an undetermined bug in Installer which does something screwy to one of the tooltypes when it writes it on some machines (probably related to the version of Installer you are using), but I can't remember which one off-hand - and it isn't a visible problem.

NB: Facts does not crash if the TCP/IP stack is not running when you start it up.  It may crash for other reasons. :shrug:

Chris