gotta say.. so long ME

On Wed, 11 Jul 2007 15:17:44 -0400, "webster72n"
cquirke wrote
On Wed, 11 Jul 2007 09:28:03 +0100, "Mike M"

and problematic with AGP video

That's a new one that could well be down to your system

I was wondering about that, too. If he said "PCI Express" instead of
"AGP" I'd be less surprised,

I have 512M's with no side effects, cquirke, but my AGP is disabled.

What motherboard chipset?

I ask, because some may need drivers for the AGP slot itself, and only
then will the display card's drivers "take".

This applies to SiS 650 etc. in XP, and some VIA chipsets need
"all-in-one" drivers too, so check out those things.

That's assuming you mean "AGP is '!' in Device Manager".

If AGP is really disabled (red-X'd, not !'d) in Device Manager, then
try enabling it again, etc.

Else you may have the AGP disabled in CMOS setup; check that.


--------------- ----- ---- --- -- - - -
Never turn your back on an installer program
--------------- ----- ---- --- -- - - -

"cquirke (MVP Windows shell/user)" wrote in
message news
On Wed, 11 Jul 2007 15:17:44 -0400, "webster72n"
cquirke wrote
On Wed, 11 Jul 2007 09:28:03 +0100, "Mike M"

and problematic with AGP video

That's a new one that could well be down to your system

I was wondering about that, too. If he said "PCI Express" instead of
"AGP" I'd be less surprised,

I have 512M's with no side effects, cquirke, but my AGP is disabled.

What motherboard chipset?

I ask, because some may need drivers for the AGP slot itself, and only
then will the display card's drivers "take".

This applies to SiS 650 etc. in XP, and some VIA chipsets need
"all-in-one" drivers too, so check out those things.

That's assuming you mean "AGP is '!' in Device Manager".

If AGP is really disabled (red-X'd, not !'d) in Device Manager, then
try enabling it again, etc.

Else you may have the AGP disabled in CMOS setup; check that.

It's not in Device Manager at all and to enable it in CMOS, I would have to
have a card, I believe, because the slot is empty. I remember trying to get
one in the past and certain problems arose (don't recall what exactly). I am
using VIA "all-in-one" drivers. If you need specific info, please let me
know and, thanks for caring.


--------------- ----- ---- --- -- - - -
Never turn your back on an installer program
--------------- ----- ---- --- -- - - -

Well, I'm pleased (and somewhat relieved) to report that FDISK /MBR worked
as predicted - Thanks again Shane, seems YM was the same as mine and thanks
also for treading the path first, around this potential MBR 'pitfall' with
Linux. Got my C: back again - no trouble - and re-Fdisked & Formatted the
D: and all is well running WinMe again.

Regarding Ogg's (and Alias's) helpful suggestion of using a Linux OS more
compatible with a 200 MHz CPU. Thanks, I take it in the spirit offered but
feel it to be a retrograde step, as this particular box has always run WinMe
without any trouble and especially considering all the odd-ball gizmos I've
got hanging onto it!!

Further, my albeit brief tippy-toe into the world of Linux (well Ubuntu)
left me somewhat underwhelmed, nay disappointed. I found that the numerous
crashes and failing re-boots I encountered - and there were quite a few
resulting from more than a couple of different (self-inflicted?) reasons -
left me with no option but to re-install each time. Even the so-called
'recovery' option would hang. Very frustrating! Probably due to ignorance,
but I couldn't find any (local) tools to trouble-shoot with. Maybe I should
have done more homework first. But at least WinMe (and the Win9x series)
offers the user/installer the option of creating a startup disk. Those tools
incorporated on the startup disk have always got me out of any Win9x
'pitfalls'.

Mart



"Mart" wrote in message
...
Shane wrote

You know the pitfall of FDISK /MBR. Having said that, I've always
successfully recovered from the Linux boot manager with it (as you well
know YMMV).

Thanks Shane, I did wonder if that was the way to go but was a little
apprehensive at this stage - hence the request for help g I'll try that
as a next to last resort before a complete FDISK etc.if neccessary and
hope that MyMMV in sync with yours. I'll probably play with Ubuntu for
another day or two - but I'm getting a bit pi**ed-off with it now and wait
for v12.12

FYI - The default (or duhfault, as Chris calls it - I like that)
installation was to 'guide' me to install to the D: drive - which was my
intention (although I was hoping that a change in the BIOS boot-order
making D: the first drive, would have been sufficient - Wrong!). So back
to the C: first, where I discovered that the 'invisible' Linux boot
manager had installed itself. Then I was left with no choice 8((

Harry, - if you're watching - DON'T go the two disk (dual boot) route.
Just start with an old 'spare' in place of the existing (known good and
working) C: and don't even consider a second disk at this stage! You can
easily replace the disk if Ubuntu goes pear-shaped and you'll have your
(WinMe) system back.

Mart

Glad it worked, Mart!


Shane

Mart wrote:
Well, I'm pleased (and somewhat relieved) to report that FDISK /MBR
worked as predicted - Thanks again Shane, seems YM was the same as
mine and thanks also for treading the path first, around this
potential MBR 'pitfall' with Linux. Got my C: back again - no
trouble - and re-Fdisked & Formatted the D: and all is well running
WinMe again.
Regarding Ogg's (and Alias's) helpful suggestion of using a Linux OS
more compatible with a 200 MHz CPU. Thanks, I take it in the spirit
offered but feel it to be a retrograde step, as this particular box
has always run WinMe without any trouble and especially considering
all the odd-ball gizmos I've got hanging onto it!!

Further, my albeit brief tippy-toe into the world of Linux (well
Ubuntu) left me somewhat underwhelmed, nay disappointed. I found that
the numerous crashes and failing re-boots I encountered - and there
were quite a few resulting from more than a couple of different
(self-inflicted?) reasons - left me with no option but to re-install
each time. Even the so-called 'recovery' option would hang. Very
frustrating! Probably due to ignorance, but I couldn't find any
(local) tools to trouble-shoot with. Maybe I should have done more
homework first. But at least WinMe (and the Win9x series) offers the
user/installer the option of creating a startup disk. Those tools
incorporated on the startup disk have always got me out of any Win9x
'pitfalls'.
Mart



"Mart" wrote in message
...
Shane wrote

You know the pitfall of FDISK /MBR. Having said that, I've always
successfully recovered from the Linux boot manager with it (as you
well know YMMV).

Thanks Shane, I did wonder if that was the way to go but was a little
apprehensive at this stage - hence the request for help g I'll
try that as a next to last resort before a complete FDISK etc.if
neccessary and hope that MyMMV in sync with yours. I'll probably
play with Ubuntu for another day or two - but I'm getting a bit
pi**ed-off with it now and wait for v12.12

FYI - The default (or duhfault, as Chris calls it - I like that)
installation was to 'guide' me to install to the D: drive - which
was my intention (although I was hoping that a change in the BIOS
boot-order making D: the first drive, would have been sufficient -
Wrong!). So back to the C: first, where I discovered that the
'invisible' Linux boot manager had installed itself. Then I was left
with no choice 8(( Harry, - if you're watching - DON'T go the two disk
(dual boot)
route. Just start with an old 'spare' in place of the existing
(known good and working) C: and don't even consider a second disk at
this stage! You can easily replace the disk if Ubuntu goes
pear-shaped and you'll have your (WinMe) system back.

Mart

On Mon, 16 Jul 2007 16:01:43 -0400, "webster72n"
"cquirke )"

What motherboard chipset?

I ask, because some may need drivers for the AGP slot itself, and only
then will the display card's drivers "take".

This applies to SiS 650 etc. in XP, and some VIA chipsets need
"all-in-one" drivers too, so check out those things.

That's assuming you mean "AGP is '!' in Device Manager".

If AGP is really disabled (red-X'd, not !'d) in Device Manager, then
try enabling it again, etc.

Else you may have the AGP disabled in CMOS setup; check that.

It's not in Device Manager at all

You should see the AGP as an item in System Devices. If you don't,
then it may not be driven, and the above applies.

and to enable it in CMOS, I would have to have a card, I believe,
because the slot is empty.

On-board graphics will be AGP, and the motherboard hardware should
detect an AGP card in the slot in preference to the onboard graphics.

Unlike PCI, AGP is not a "bus" in the sense of supporting multiple
devices (in other words, you can't have two AGP devices).

The usual CMOS settings are to prioritise PCI over AGP or vice versa
(relevant if you use an old PCI display card), and possibly to disable
or enable the onboard graphics.

I remember trying to get one in the past and certain problems arose

AGP has evolved, and evolutions are usually referred to as multiples,
such as "4x" or "8x". What is significant about these generations,
from a compatibility perspective, is that the operating voltage
usually drops as the data rate multiplier goes up.

So you can find old AGP cards don't work with new AGP motherboards,
and vice versa. Hopefully there will be appropriate differences in
the notches and pegs within the card and slot, so that you would be
physically discouraged from mixing different voltage standards.

I am using VIA "all-in-one" drivers.

Oh, OK..
..
If you need specific info, please let me know

Heh - by now I'm forgetting what the original problem was :-)

What I usually see "in the field" is:
- can't set the refresh rate, which is a flickery duhfault 60Hz
- monitor refresh rate drop-down is empty or greyed out
- display details are all unknown
- the appropriate display card/chipset drivers won't "take"

In this case, the problem is usually that the motherboard chipset's
AGP drivers are not present (in your case, the VIA 4-in-1) so that the
OS cannot "see" the card and thus cannot bind the drivers to it.



--------------- ----- ---- --- -- - - -
Dreams are stack dumps of the soul
--------------- ----- ---- --- -- - - -

On Sun, 15 Jul 2007 17:43:56 -0400, "Heather"

Needle work??? Bwa ha ha!! You ARE showing your age. Women haven't
done that since the middle ages.

Maybe he meant shooting up some smack ;-)



------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

"cquirke (MVP Windows shell/user)" wrote
in message ...
On Sun, 15 Jul 2007 17:43:56 -0400, "Heather"

Needle work??? Bwa ha ha!! You ARE showing your age. Women haven't
done that since the middle ages.

Maybe he meant shooting up some smack ;-)

ROFL!! He wouldn't know what in heck that was.....not that I would
either (cough). Did I ever tell you I worked for the Provincial Drug
Prosecutor?? Maybe Har Har will get it now.

HF



------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

"cquirke (MVP Windows shell/user)" wrote in
message ...
On Sun, 15 Jul 2007 17:43:56 -0400, "Heather"

Needle work??? Bwa ha ha!! You ARE showing your age. Women haven't
done that since the middle ages.

Maybe he meant shooting up some smack ;-)

Don't give me any ideas, C' ...
Just because it was good in the "middle" ages, doesn't mean it isn't good
anymore.




------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

"cquirke (MVP Windows shell/user)" wrote in
message ...
On Mon, 16 Jul 2007 16:01:43 -0400, "webster72n"
"cquirke )"

What motherboard chipset?

I ask, because some may need drivers for the AGP slot itself, and only
then will the display card's drivers "take".

This applies to SiS 650 etc. in XP, and some VIA chipsets need
"all-in-one" drivers too, so check out those things.

That's assuming you mean "AGP is '!' in Device Manager".

If AGP is really disabled (red-X'd, not !'d) in Device Manager, then
try enabling it again, etc.

Else you may have the AGP disabled in CMOS setup; check that.

It's not in Device Manager at all

You should see the AGP as an item in System Devices. If you don't,
then it may not be driven, and the above applies.

and to enable it in CMOS, I would have to have a card, I believe,
because the slot is empty.

On-board graphics will be AGP, and the motherboard hardware should
detect an AGP card in the slot in preference to the onboard graphics.

Unlike PCI, AGP is not a "bus" in the sense of supporting multiple
devices (in other words, you can't have two AGP devices).

The usual CMOS settings are to prioritise PCI over AGP or vice versa
(relevant if you use an old PCI display card), and possibly to disable
or enable the onboard graphics.

I remember trying to get one in the past and certain problems arose

AGP has evolved, and evolutions are usually referred to as multiples,
such as "4x" or "8x". What is significant about these generations,
from a compatibility perspective, is that the operating voltage
usually drops as the data rate multiplier goes up.

So you can find old AGP cards don't work with new AGP motherboards,
and vice versa. Hopefully there will be appropriate differences in
the notches and pegs within the card and slot, so that you would be
physically discouraged from mixing different voltage standards.

I am using VIA "all-in-one" drivers.

Oh, OK..
.
If you need specific info, please let me know

Heh - by now I'm forgetting what the original problem was :-)

What I usually see "in the field" is:
- can't set the refresh rate, which is a flickery duhfault 60Hz
- monitor refresh rate drop-down is empty or greyed out
- display details are all unknown
- the appropriate display card/chipset drivers won't "take"

In this case, the problem is usually that the motherboard chipset's
AGP drivers are not present (in your case, the VIA 4-in-1) so that the
OS cannot "see" the card and thus cannot bind the drivers to it.

My BIOS shows the AGP Driving value fixed at '64' with an 'x' to the left.
According to SiSoft I have one PCI/AGP Bus each.
The 4-in-1 drivers are installed.
And there is no mention of AGP in Device Manager.
Since everything is working allright, I might as well forget about this.




--------------- ----- ---- --- -- - - -
Dreams are stack dumps of the soul
--------------- ----- ---- --- -- - - -

"webster72n" wrote in message
...

"cquirke (MVP Windows shell/user)" wrote
in
message ...
On Sun, 15 Jul 2007 17:43:56 -0400, "Heather"

Needle work??? Bwa ha ha!! You ARE showing your age. Women
haven't
done that since the middle ages.

Maybe he meant shooting up some smack ;-)

Don't give me any ideas, C' ...
Just because it was good in the "middle" ages, doesn't mean it isn't
good anymore.

Hate to burst your bubble, Har.....but "smack" was not around in the
middle ages. It was not refined enough until the turn of the century
(1900). It is a morphine derivative.

And I am taking a giant leap of faith here in assuming you knew what in
heck "smack" was. Your answer is suitably Harry-vague-ish enough to
conclude that you didn't know, grin.




------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -