I was also inclined to be charitable, but the more I thought about it, the less so. There's no actual need to boot it; the machine has a battery refresh program built right into BIOS (nifty feature, by the way) which revealed the problem quite clearly. OK, even so, boot it up once or twice ... three times, even, but not day after day after day.
The thing did come back with a CD in the reader, labeled "Windows Burn-in CD", so I suspect they finally figured out that it wasn't Windows and booted from a CD to run their diagnostics. They could have done this right at the outset. Could this have been the first time they ever saw Linux on one of their machines? They also assigned two different RMA's, this may have been the cause of the communications problem. Judah Alexander Mahabir <[EMAIL PROTECTED]> wrote: > No matter how qualified you are, and how thoroughly you diagnosed the > machine to pinpoint the problem, most companies would re-diagnose the > problem, to see if it's something else. Maybe this is what they were doing? > trying to find software fault, or fault elsewhere. > > On 10/2/05, J. Milgram <[EMAIL PROTECTED]> wrote: > > > > OK, it's back. I sent them an email and left a voicemail at corporate HQ > > and it was sent via overnight within a day or two after that. > > > > I was all set to announce them as "rehabilitated" ... but on looking at > > the system logs, it seems that they had been booting it up every couple > > of days, with quite a number of root logins during the course of the > > month they had it (during which time they were unable to tell me > > anything about it). This was just for a new battery, so what's going on > > here? Obviously it wasn't sitting around for a month waiting its > > turn. Why do they need to boot it up at all to test the battery? So I > > think I'll leave them in "goat" status. That's Averatec, a-v-e-r- ... > > > > (I had removed the root password so they could have free access to it in > > case they needed to do any diagnostics ... and did have the foresight to > > run md5sums on everything. They checked out OK on return.) > > > > BTW, it's a good machine, other than this one issue. Someone suggested I > > probably could have just sent in the battery w/out the machine. > > > > Judah > > > > > > J. Milgram <[EMAIL PROTECTED]> wrote: > > > > > That's a good one. > > > > > > I'm ramping it up, bit by bit, rather than go nuclear all at once :) > > > > > > BTW I did index it at google and yahoo, that was a good idea. > > > > > > David Zakar <[EMAIL PROTECTED]> wrote: > > > > > > > Seems like Slashdot will print practically anything these days - > > article > > > > submission time? > > > > > > > > "Ask Slashdot: I've recently noticed that computer vendors are taking > > > > longer and longer to fulfill their warranty obligations. As > > > > <yourlink>my</yourlink> experience shows, this can be a major drain on > > > > productivity, and feedback on where the computer is in the process. > > What > > > > can I do to speed things up?" > > > > > > > > Or you could put an anti-American screed in it, and K5 will print it > > for > > > > sure! > > > > > > > > -DMZ > > > > > > > > On Wed, 2005-09-21 at 21:51 -0400, as wrote: > > > > > hi, > > > > > > > > > > will it not help if it shows up on google/ yahoo search - it will > > > > > probably help to have a high page rank or link from a page that > > does. > > > > > > > > > > my 2 cents. > > > > > > > > > > aravind. > > > > -- > > > > David Zakar <[EMAIL PROTECTED]> > > > > > > > > >
