A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows ME » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

gotta say.. so long ME



 
 
Thread Tools Display Modes
  #91  
Old July 21st 07, 03:44 AM posted to microsoft.public.windowsme.general
Shane
External Usenet User
 
Posts: 480
Default gotta say.. so long ME

webster72n wrote:
"cquirke (MVP Windows shell/user)"
wrote in message news
On Tue, 17 Jul 2007 19:23:18 -0400, "webster72n"

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.


Agreed... "tip-toe away quietly" ;-)

Tho it's disturbing in the sense of interpreting answers to questions
one might ask that aim to find out whether a user's AGP base drivers
are in place, in the context where all is not well (e.g. "I can't
install my display drivers, they just don't 'take' when I try")


According to 'SiSoft' and/or 'Aida32' and/or 'Everest' HE the drivers
are installed, I 'm just unable to manipulate it in the BIOS, which
means to me: leave it alone.


So, it's faint rather than bold, Harry? (I can't think what you actually
call it other than 'greyed out' and its extremely unlikely to be a shade of
grey!) If it's bold, you should be able to change it (x64 seems a little
high for onboard - but then, unlike Chris, I'm not a system builder, and if
he says its normal...). If 'greyed out' (alright, I'm going for grey after
all) I'd have thought it means installed but access deemed unnecessary. This
machine had onboard - first I've had - but I wasn't interested changing
anything until I'd fitted a card, so I haven't actually seen that you can
change the multiplier with onboard video. Again, if Chris says you can,
that's good enough for me.

I do know that even with 128MB on the card it may be better having x64
selected because this isn't a setting like you expect it to be whereby the
bigger is always better. Trying to think how to explain it but all I can
think of is polarised light waves.

Shane


  #92  
Old July 21st 07, 04:34 AM posted to microsoft.public.windowsme.general
webster72n
External Usenet User
 
Posts: 1,526
Default gotta say.. so long ME


"Shane" wrote in message
...
webster72n wrote:
"cquirke (MVP Windows shell/user)"
wrote in message news
On Tue, 17 Jul 2007 19:23:18 -0400, "webster72n"

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.

Agreed... "tip-toe away quietly" ;-)

Tho it's disturbing in the sense of interpreting answers to questions
one might ask that aim to find out whether a user's AGP base drivers
are in place, in the context where all is not well (e.g. "I can't
install my display drivers, they just don't 'take' when I try")


According to 'SiSoft' and/or 'Aida32' and/or 'Everest' HE the drivers
are installed, I 'm just unable to manipulate it in the BIOS, which
means to me: leave it alone.


So, it's faint rather than bold, Harry? (I can't think what you actually
call it other than 'greyed out' and its extremely unlikely to be a shade

of
grey!) If it's bold, you should be able to change it (x64 seems a little
high for onboard - but then, unlike Chris, I'm not a system builder, and

if
he says its normal...). If 'greyed out' (alright, I'm going for grey after
all) I'd have thought it means installed but access deemed unnecessary.

This
machine had onboard - first I've had - but I wasn't interested changing
anything until I'd fitted a card, so I haven't actually seen that you can
change the multiplier with onboard video. Again, if Chris says you can,
that's good enough for me.

I do know that even with 128MB on the card it may be better having x64
selected because this isn't a setting like you expect it to be whereby the
bigger is always better. Trying to think how to explain it but all I can
think of is polarised light waves.

Shane


Here it goes Shane, the details:

'AGP Aperture size' in bold and set at 64M
'AGP Driving Control' in bold and set at 'Auto'.
'xAGP Driving Value' faint and 'set at 64'.
'AGP Master 1 WS Write' in bold and disabled
'AGP Master 1 WS Read' in bold and disabled.

The four settings 'in bold' I can control, the driving value not, probably
because it's 'on board'. Maybe this will shed some light on the situation.

Harry.





  #93  
Old July 22nd 07, 12:27 AM posted to microsoft.public.windowsme.general
Shane
External Usenet User
 
Posts: 480
Default gotta say.. so long ME

Harry,

Driving Value is faint (you can't change it) because Driving Control is set
to Auto. Set to (presumably) Manual, you would be able to alter it - but,
while you have to 'Save Changes and Exit' to actually affect anything, this
is a value you can fry things by setting wrong, ie 'overclocking'. As it
does work, leave it alone.



Shane


Here it goes Shane, the details:

'AGP Aperture size' in bold and set at 64M
'AGP Driving Control' in bold and set at 'Auto'.
'xAGP Driving Value' faint and 'set at 64'.
'AGP Master 1 WS Write' in bold and disabled
'AGP Master 1 WS Read' in bold and disabled.

The four settings 'in bold' I can control, the driving value not,
probably because it's 'on board'. Maybe this will shed some light on
the situation.





  #94  
Old July 22nd 07, 03:44 AM posted to microsoft.public.windowsme.general
webster72n
External Usenet User
 
Posts: 1,526
Default gotta say.. so long ME


I did try that already, Shane, with no consequence.
Hence I gave it up.


"Shane" wrote in message
...
Harry,

Driving Value is faint (you can't change it) because Driving Control is

set
to Auto. Set to (presumably) Manual, you would be able to alter it - but,
while you have to 'Save Changes and Exit' to actually affect anything,

this
is a value you can fry things by setting wrong, ie 'overclocking'. As it
does work, leave it alone.



Shane


Here it goes Shane, the details:

'AGP Aperture size' in bold and set at 64M
'AGP Driving Control' in bold and set at 'Auto'.
'xAGP Driving Value' faint and 'set at 64'.
'AGP Master 1 WS Write' in bold and disabled
'AGP Master 1 WS Read' in bold and disabled.

The four settings 'in bold' I can control, the driving value not,
probably because it's 'on board'. Maybe this will shed some light on
the situation.







  #95  
Old July 22nd 07, 01:42 PM posted to microsoft.public.windowsme.general
Shane
External Usenet User
 
Posts: 480
Default gotta say.. so long ME

Did what, Harry? Apart from the fact I'm telling you not to do anything. Are
you playing with the CMOS these days?

If you're going to press every button just because you can, can I ask you to
make some audio recordings? 'Cause we won't hear it from here.

Shane


webster72n wrote:
I did try that already, Shane, with no consequence.
Hence I gave it up.


"Shane" wrote in message
...
Harry,

Driving Value is faint (you can't change it) because Driving Control
is set to Auto. Set to (presumably) Manual, you would be able to
alter it - but, while you have to 'Save Changes and Exit' to
actually affect anything, this is a value you can fry things by
setting wrong, ie 'overclocking'. As it does work, leave it alone.



Shane


Here it goes Shane, the details:

'AGP Aperture size' in bold and set at 64M
'AGP Driving Control' in bold and set at 'Auto'.
'xAGP Driving Value' faint and 'set at 64'.
'AGP Master 1 WS Write' in bold and disabled
'AGP Master 1 WS Read' in bold and disabled.

The four settings 'in bold' I can control, the driving value not,
probably because it's 'on board'. Maybe this will shed some light on
the situation.



  #96  
Old July 22nd 07, 07:49 PM posted to microsoft.public.windowsme.general
webster72n
External Usenet User
 
Posts: 1,526
Default gotta say.. so long ME

Shane:

At one time I did set it to manual, but since it asks for a hex # to be
keyed in, I abandoned any further attempts, because I don't know of such a
number.
What specific recordings would you like to hear, a f**t perhaps?
Stay tuned...

Harry.


"Shane" wrote in message
...
Did what, Harry? Apart from the fact I'm telling you not to do anything.

Are
you playing with the CMOS these days?

If you're going to press every button just because you can, can I ask you

to
make some audio recordings? 'Cause we won't hear it from here.

Shane


webster72n wrote:
I did try that already, Shane, with no consequence.
Hence I gave it up.


"Shane" wrote in message
...
Harry,

Driving Value is faint (you can't change it) because Driving Control
is set to Auto. Set to (presumably) Manual, you would be able to
alter it - but, while you have to 'Save Changes and Exit' to
actually affect anything, this is a value you can fry things by
setting wrong, ie 'overclocking'. As it does work, leave it alone.



Shane


Here it goes Shane, the details:

'AGP Aperture size' in bold and set at 64M
'AGP Driving Control' in bold and set at 'Auto'.
'xAGP Driving Value' faint and 'set at 64'.
'AGP Master 1 WS Write' in bold and disabled
'AGP Master 1 WS Read' in bold and disabled.

The four settings 'in bold' I can control, the driving value not,
probably because it's 'on board'. Maybe this will shed some light on
the situation.





  #97  
Old July 23rd 07, 01:52 AM posted to microsoft.public.windowsme.general
Shane
External Usenet User
 
Posts: 480
Default gotta say.. so long ME

OK Harry,

At one time I did set it to manual, but since it asks for a hex # to
be keyed in, I abandoned any further attempts, because I don't know
of such a number.


Really? Interesting.

What specific recordings would you like to hear, a f**t perhaps?
Stay tuned...


LOL!

I must admit I feel extremely childish saying eg, v. good, to that, but v.
good anyway!


Shane


  #98  
Old July 23rd 07, 06:53 PM posted to microsoft.public.windowsme.general
webster72n
External Usenet User
 
Posts: 1,526
Default gotta say.. so long ME


"Shane" wrote in message
...
OK Harry,

At one time I did set it to manual, but since it asks for a hex # to
be keyed in, I abandoned any further attempts, because I don't know
of such a number.


Really? Interesting.


What's so interesting about that, Shane??


What specific recordings would you like to hear, a f**t perhaps?
Stay tuned...


LOL!

I must admit I feel extremely childish saying eg, v. good, to that, but v.
good anyway!


Childish we are and 'childlike' we shall remain.
How else can we keep our hopes alive?
BTW a couple of years ago I updated my BIOS with help from the 'proper'
sources in the form of a 'floppy disk' and no problems whatsoever.
To preempt any thoughts in this direction, the AGP situation was
'preexisting'.
Keep in mind to never underestimate the child in you. H.



Shane




  #99  
Old July 24th 07, 01:25 AM posted to microsoft.public.windowsme.general
webster72n
External Usenet User
 
Posts: 1,526
Default gotta say.. so long ME


"webster72n" wrote in message
...

"Shane" wrote in message
...
OK Harry,

At one time I did set it to manual, but since it asks for a hex # to
be keyed in, I abandoned any further attempts, because I don't know
of such a number.


Really? Interesting.


What's so interesting about that, Shane??


What specific recordings would you like to hear, a f**t perhaps?
Stay tuned...


LOL!

I must admit I feel extremely childish saying eg, v. good, to that, but

v.
good anyway!


Childish we are and 'childlike' we shall remain.
How else can we keep our hopes alive?
BTW a couple of years ago I updated


should read: "upgraded", of course.

my BIOS with help from the 'proper'
sources in the form of a 'floppy disk' and no problems whatsoever.
To preempt any thoughts in this direction, the AGP situation was
'preexisting'.
Keep in mind to never underestimate the child in you. H.



Shane






 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Invalid long filename General 10 October 19th 05 07:11 AM
Long boot Dale General 11 July 28th 04 03:22 AM
A very long message ppoatt General 18 July 3rd 04 07:43 PM
Share name to long for ME Herb Networking 2 June 10th 04 04:41 PM
Long shut down Jim Y Improving Performance 0 May 6th 04 10:00 PM


All times are GMT +1. The time now is 02:17 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.