@AmiKit

Replace the cell battery, its dropped below the voltage required to maintain uboot. And yes, it will work one minute & be dead the next & it happens just as you change something.

@AmiGame

On June 9th, the site showed exactly 500 members & DonF was the only one at that time that had signed up (at that point). Seems the other 2 showed up later. If that's true, then the list for the 9th is 1st to last signing up on that day. Sounds backwards, but thats what I saw.

There must be a time stamp log for new members.

@AJS

I would say that DonF was #500. I was on the site when it read 500 members & Don was the lastest (date wise) to sign up, but I would imagine the site logs would have to be looked at anyway.

@afxgroup

Quote:


What is the difference between Mencoder & ffmpeg? They both appear to do the same things.

@Valiant

Just noticed that v2.2 doesn't record the time right. 1034 in 3:00 min, 1034 in 3:42 min recorded with os4 final.

@tonyw

Like you, I've had the same problem & I keep trying different things. For a month now I've had very few GRs. What seemed to help was to turn off the disk cache & put IB on the black list. I still have IB on the black list, but I've since set up the cache in ram: so it's not saved if I turn the system off. I'm wondering if there's a bug in the cache when using the SFS file system. The recoverable alert on quitting seems to be with the new memory system.

@Atheist

No, check sys:storage/dosdrivers & move RAD to sys:devs/dosdrivers, ud4 & final.

@lazi

Confirmed, I get a total system freeze here.

@COBRA

It's available for download now & ppl can select the "upload" link & grab a file from there before it's checked.

@All

Well after replacing my 512Mb mem stick with the original 256 that came with my micro, IB still gives me GR'ers on start & quitting.

One other thing that I wonder about is I have 2 keys, 1 for v1.x & another for v2.x. Both are required to unlock IB & I'm wondering if that can cause problems with v2.4.

@Jack

Sorry for the confusion guys, I have a micro with a G3 GX. I was thinking that the clock was generated on the board by a crystal like on a classic, but after reading the cpu specs, I see that the clock is generated by the cpu chip itself. NOW I understand how a higher frequency cpu can replace a lower frequency cpu. Getting slow in my old age.

@Swisso

Where is the clock frequency generated on the micro? I see 2 crystals on the board, but my docs don't mention any settings above 933MHZ. Will any A1 support a 1.7GHZ cpu? If so, what is the upper limit?

@AmigaPapst

I do know that ack had a couple of cpu modules working & he gave a lot of info on the design in irc. He had a 750GL G3 @ 1.2GHz that would have cost around $250US. I would jumped all over that it they ever become available. Adam seems to have gone into hiding as of late & the status of his cpu modules is un-known.

@Tomcat

2.2V would defininitely give you a black screen. Custom uboot settings may need to be set again like DMA & h/w config variables. If you used uboot prefs to save your settings first, you would just load the file back & save.

@Tomcat

Don't think ram would cause that, but a weak cell battery sure would. If the battery voltage falls below 2.95V you'll start to have problems like that. If you pull the battery for replacement, leave it out for 10 min to re-set uboot. Before pulling the battery, open a shell & type nvgetvar >prt: to get a hard copy on paper & then I open uboot prefs & there's a menu option to save your setting to a file on disk that can be re-loaded back & saved as the h/w configuration setting will be lost.

I haven't had an IB startup crash since going back to the original 256MB mem stick, but I still get the odd recoverable alert when quitting.

@tonyw

The 750 G3/GL is what ack was using in his new cpu module, it's what the GX should have been.

@tonyw

So far no GRs with the original 256MB memory stick, but it's only the first day. I'd be both happy & sad if my 512MB stick was the problem. If thats the case, we really would need a better memory tester. Just seemed to me that ppl that were having a problem with IB had a G3 750GX with 512M of memory. Going to ba an interesting weekend.

@Tomcat

I installed the 040 version with the ppc version of the javascript.library. I do get random crashes starting & quitting IB. I just now re-installed my original 256MB memory stick to see if my 512MB memory stick is the problem. The 512MB stick passes memtester, but this is a much better test.

Start NotePad & type 256, save this as SYS:Prefs/Env-Archive/REAPER.68KStackTrace, copy the file to ENV: as well.
I also tried removing JIT from kickstart, but still got the GRs on startup. I was told to delete my cache & re-install IB, working so far now with JIT.

@greeneagle

I use NotePad for printing text files. With TurboPrint active, NP refuses to print until I turn TP off. Another thing I found was if I config Printer prefs then config TP, my Printer prefs changes or if I config TP, my Printer prefs changes. In other words the 2 pref settings interact. Because of that,I removed TP from WBStartup & activate it only to print gfx or pdf's.