Registered: Sep 2000
Location:
Posts: 117

I had been having a rash of 0x308 errors and I recently built up my files from scratch again and found that the 0x308 errors did not start recurring until I put Blazer back on the system and starting using it. Anybody else have this problem?

Registered: Jan 2001
Location:
Posts: 125

OmniSky told me that it was just a quirk and the best way to get rid of it was to reset the visor with the minstrel attached. I use Blazer with my Prism and Minstrel with no problems.

Registered: Sep 2000
Location:
Posts: 117

quirk?--that's too funny.

"quirk"? That, along with "fluke" and "glitch" are codewords for "we have no frickin' clue"--it does not mean "it's an isolated occurrence". I used to get these errors constantly, all the while Blazer was my favorite browser. Warm booting is not a solution. Plus, that's not always convenient. The reset pin provided with the stylus will NOT reach the switch when then Minstrel is in the Visor. I use Launch'em's soft warm-boot function when I'm not totally hung, but other than that, I have to hope I have a paper clip nearby. I honestly have had a total absense of these errors since I stopped using Blazer--I find it hard to believe that nobody else has come across this.

Registered: Sep 2000
Location: Cascade, MD
Posts: 74

A tech at YY told me (after I had a nasty crash and called them) that there is a known conflict with Blazer and the Minstrel S, but I still prefer Blazer and use it...for now.

L.

[Edited by lowtech on 01-19-2001 at 06:10 AM]