I probably won't be playing with it any longer since I'm seeing a lot of
other problems, which I do not have thankfully, caused by this last update,
right or wrong. I replicated it the one time for GPs, and after a cold
boot, but since there's no way to tell what else it might be doing, I'm not
inclined to play much more with it. I have a laptop with XP Home that I use
as a test bed sometiimes, and it had no problems with the SATA label that I
could tell.
I think I neglected to mention that this happened on XP Pro, and I do
have apps from Norton installs in place. GoBack is iffy while this problem
exists, so if you have it, use it sparingly or not at all. Somehow, just
before I got into the looping boots, it must have put a run-once entry in
memory somehow because I couldn't even boot from my Ghost CD without the
GoBack message coming up, and of course the boots failed and looped again.
I had to completely remove power from the machine to get rid of it. From a
full cold boot the CD finally booted properly. Nothing to do with SATA, but
a point of interest, at least for me.
I would be interested whether I'm the only one with this issue or not. I've
watched the groups and haven't seen anyone else comment on it so perhaps I'm
a "one-off" for some reason.
Alt-255 in a directory name; I used to put it in file names, but don't think
I ever used it in a directory. Days were so much simpler back in CP/M times
too! My first experience was with an IMSI 8080 with dual 9" 90k floppies,
writing Basic programs for our engineering inventory!
Regards,
Pop`
Neal at Spectdar Computing wrote:
> This is a most interesting post. Judging by your nic I think it's
> safe to say we've both been around the block a few times. I've never
> heard of this before. It's late on Saturday night and usually I'd go
> on down to the shop to reproduce the incident. But I will do exactly
> that on Monday. I did manage to trash a system back in MsDos days by
> using alt+255 as part of a drive label. If you plan on playing around
> with this stay in touch. I'm very interested in the outcome.
> Neal
>
> "Poprivet" wrote:
>
>> Hi guys & gals,
>>
>> It took awhile to work out, but apparently as of the last updates,
>> you can not use "SATA" as a drive label. I didn't know labels
>> mattered. It did, at least in my case here. XP Pro, SP2+, home
>> LAN, 3 machines. It's repeatable now I've got everything back to
>> status quo. When I put my SATA drive in a few months ago, I used
>> E SATA, F SATA and G SATA for the drive labels. All of a sudden
>> last Tuesday after the updates I started getting chkdsk running on E
>> and G at every boot and eventually it quit booting and got into the
>> looping I also see referenced here. It ended up trashing both the
>> PATA and SATA drives! Luckily I have them imaged! As I
>> troubleshot I got to the pont where I couldn't boot or even get to
>> Safe Mode or to the command prompt! It'd start and then loop back
>> and start again every time, no matter what I chose, including last
>> known good. Go figger! Long story short, I finally renamed the
>> drives since I'd been meaning to for a long time anyway and it was
>> convenient, and darned if all the problems didn't go away! I then
>> reloaded the latest images/incrementals and all was fine. And still
>> is today.
>>
>> I'm reasonably certain my machines were all clean; update and run AV,
>> adaware, spybot, WinPatrol and another I can't think of the name of
>> right now, each night.
>>
>> Regards,
>>
>> Pop`
|
Similar Threads
Linear Mode
