CompuServe Thread

Adspeed problem

8 messages in this thread
#45113From: Dan ColeJan 2, 1992 7:54 PM
I just installed Adspeed on my A500 with a GVP series II harddrive(Igot the right rom chip), Workbench 2.0. Everything seems to work except when the harddisk boots up I get a message indicating that Adspped has not yet returned, and the requestor wants to know if I want to wait or not. What's that mean, and what do I do about it? Thanks.
#45175From: ICD, Inc.Jan 3, 1992 6:25 AM
I don't know what you mean by "Adspeed has not yet returned". What program is giving you this message? Craig
#45186From: Richard GraffJan 3, 1992 9:47 AM
He is talking about a systems requester during bootup, I had the same problem for a while with a Xetec harddrive, I can't set the adspeed to hardware boot at 14mhz with my system, running the ADspeed utility is what caused the System requestor. It doesn't do it now, but I can't remember why it stopped. -Rick Graff
#45182From: Michael GerardJan 3, 1992 9:28 AM
Dan: If you are starting AdSpeed from the WB, open up the adspeed icon with the WB info menu choice and add a new tooltype: DONOTWAIT… if you're starting it from your startup-sequence, add DONOTWAIT after the AdSpeed command. – Whapp!ng from the North Coast Michael
#45185From: Richard GraffJan 3, 1992 9:46 AM
When I first installed my ADspeed, I had the same problem with 2.0 and a Xetec Fastrak harddrive. It doesn't do it now, although I can't remember why, I had quite a bit of problems with my harddrive when i first installed 2.0. I have things set up now that the ADspeed is hardware set to run inn 7mhz mode and then in the User-Startup file in my S/ directory, I have the line: ADspeed ON This software sets the adspeed to be running at 14mhz by the time the boot is finished. The Adspeed utility is in my C/ directory. -Rick Graff
#45230From: Alan WheltonJan 3, 1992 8:58 PM
Unrelated to your current problem, but did you fix the problem you had with the new 2.04 ROM installation? Just wondering what the fix was. 🙂
#45250From: Dan ColeJan 3, 1992 11:52 PM
Yeah thaanks to somebody here I did fix it. Seems that when you install a 1 meg Agnus to an A500. There are two ways to docter the motherboard so the machine recognizes 1 meg of chip ram. A Commodore authorized dealer made the adjustment to my board and I've since learned he picked the easy fast and not recommended way which includes screwing aroung with the Gary chip. The recommended way involves cutting a jumper. When I learned that, I bought a new Gary ($17), installed it, cut the jumper and low and behold, 2.0 works. Dan Cole
#45310From: Alan WheltonJan 4, 1992 9:26 PM
Well, so that was the problem. I installed my 1 Meg Agnus last year and went the route of swapping chips then cutting the trace on the motherboard. Thanks for the information. Never know when one might run into a similar situation. Happy computing! <G>