Support
Looper's Delight
|
Support |
|
|
Mark- over the years of dealing with this thing in excruciating detail I've gotten a pretty good idea of which sorts of failures are hardware and which are software. In this case, like Bret said, you have firmware that is booting up perfectly fine in a large number of units. Then you have one hardware unit out of many that develops a sporadic crashing problem. Chances are it is something specific with that hardware, since the software is the same as everywhere else. History has shown that this specific type of bootup crash is usually related to the memory or the ROMs not contacting properly for some reason. That could be due to a bent pin, dirty or oxidized contacts in a socket, or a broken solder joint. Those things are relatively easy to deal with, so they are a good place to start. Also, I've designed a lot of computer hardware in my career. I've always rather enjoyed how computer users always think all crashes and problems with their systems are caused by windows crashing or bad drivers. It really takes the pressure off the hardware guys. kim At 01:17 PM 9/9/2002, sine@zerocrossing.net wrote: >Oh... and by the way, how can you be sure it's hardware and not software? >Seems like the machine is crashing, as would any computer running >software. >Getting stuck in a boot sequence seems like software, no? > >Mark Sottilaro > >Kim Flint wrote: > > > these are hardware issues, not software. almost always it turns out to >be a > > dirty memory socket or something like that. > > kim > > > > At 03:42 AM 9/9/2002, Jimmy Fowler wrote: > > >"Kim, Is ther any reason I shouldn't try to reinstall LoopIII?" > > > > > >question: are these problems only happening with LoopIV? i never >upgraded > > >and have had NO software or hardware problems at all from either >unit, one > > >being 6 months old and the other just a few weeks. ______________________________________________________________________ Kim Flint | Looper's Delight kflint@loopers-delight.com | http://www.loopers-delight.com