Warning...DON'T do what I did...

Scenario: 1. Bought a Voodoo 3 2000 2. Downloaded overclocker 3. Overclocked from 143 to 173 in small increments 4. No change in framerates ...so... 5. Overclocked to 200 to see what would happen 6. Restarted 7. Nothing but little dots on screen! 8. Restarted a few more times with same little dots ...sitting here wondering how the heck I'm going to be able to get a screen so I can disable the overclocking. Talk about a "vicious circle". I have to disable overclocker to be able to see my screen...but I have to see the screen in order to disable the overclocking. ...finally had to... 9. Turn my system off 10. Connect my monitor to my onboard video output 11. Turn on system 12. Change to "Onboard Video" in BIOS 13. Restart 14. Uninstall overclocker 15. Restart 16. Go back into BIOS and set video back to 3dfx 17. Shut down 18. Connect my monitor back to 3dfx card output 19. Restart 20. Everything works fine now 21. Decided that I will NEVER do that again! Pops...

hehey, 200 was never gonna work. My 3000 stops at just over 190. Though I only run it at 175. Pops <[email hidden]> wrote in message news:zuxr5.2$[email hidden]...

Quoted text (12 lines)

> Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a

screen

Quoted text (23 lines)

> so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > >

In article <zuxr5.2$[email hidden]>, [email hidden] says...

Quoted text (36 lines)

> Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a screen > so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > > >

Have done that ;) but I only started in failsafe mode (win98) and adjusted the overclocking utility's ini file to a decent MHz. -- Greetings Johan N [email hidden]

Why, wouldn't it run in Safe mode? -- Slot Tweaks & Reviews www.slottweak.com

lucky you didn't fry the chip -- Kieran www.pcracing.co.uk for GP3 and WSC Pops <[email hidden]> wrote in message news:zuxr5.2$[email hidden]... > Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a screen > so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > >

Here's what you should do: 1. Go buy a gun. 2. Go buy bullets. 3. Put bullets in gun. 4. Put gun to head. 5. Pull trigger. All your crazy overclocking experiments will be solved ;-) Pops <[email hidden]> wrote in message news:zuxr5.2$[email hidden]...

Quoted text (12 lines)

> Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a

screen

Quoted text (23 lines)

> so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > >

Um...200 MHz was a little much, and you should have seen a decent difference in frame rates, that is more then what the 3000 is running at, and I know that I was running faster on my 3000 then my friends 2000. Also, there is something called Safe Mode that you could have gone into :) -Stuart Becktell "Pops" <[email hidden]> wrote in message news:zuxr5.2$[email hidden]...

Quoted text (12 lines)

> Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a

screen

Quoted text (23 lines)

> so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > >

166 is the safe limit Pops <[email hidden]> wrote in message news:zuxr5.2$[email hidden]...

Quoted text (12 lines)

> Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a

screen

Quoted text (23 lines)

> so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > >

Ever heard of Safe Mode? I'm not positive that would work, but it certainly should the next time you decide to do something silly. ;) -- ----------------------------------- Morgan Vincent Wooten GPLRank: +15.49 mailto:[email hidden] http://members.tripod.com/~morganv/ ----------------------------------- Pops <[email hidden]> wrote in message news:zuxr5.2$[email hidden]... > Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a screen > so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > > >

That's a pretty serious gain you tried to get with a V3 2000. Did you run it for a good length of time between bumping it up? -- Don Burnette Dburn in N3 and Legends ICQ# 74084566 "Pops" <[email hidden]> wrote in message news:zuxr5.2$[email hidden]... > Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen! > 8. Restarted a few more times with same little dots > ...sitting here wondering how the heck I'm going to be able to get a screen > so I can disable the overclocking. Talk about a "vicious circle". I have > to disable overclocker to be able to see my screen...but I have to see the > screen in order to disable the overclocking. > ...finally had to... > 9. Turn my system off > 10. Connect my monitor to my onboard video output > 11. Turn on system > 12. Change to "Onboard Video" in BIOS > 13. Restart > 14. Uninstall overclocker > 15. Restart > 16. Go back into BIOS and set video back to 3dfx > 17. Shut down > 18. Connect my monitor back to 3dfx card output > 19. Restart > 20. Everything works fine now > 21. Decided that I will NEVER do that again! > > Pops... > > > >

In article <zuxr5.2$[email hidden]>, [email hidden] says...

Quoted text (10 lines)

> Scenario: > > 1. Bought a Voodoo 3 2000 > 2. Downloaded overclocker > 3. Overclocked from 143 to 173 in small increments > 4. No change in framerates > ...so... > 5. Overclocked to 200 to see what would happen > 6. Restarted > 7. Nothing but little dots on screen!

******** SNIP ******* Would have been MUCH easier to just boot to Safe Mode, change to Standard VGA display and then reboot and setup your 3Dfx drivers over again. =) -- Rob [email hidden]

You have to get in safe mode during reboot. Since I'm too lazy to look up the proper keystroke, I reset during reboot. The next boot will be in safe mode. JensSchumi On Thu, 31 Aug 2000 18:29:51 GMT, "Pops" <[email hidden]> wrote: >Scenario: > >1. Bought a Voodoo 3 2000 >2. Downloaded overclocker >3. Overclocked from 143 to 173 in small increments<snip> --------------------------------------------- LWFF Ball Bearing conversion at: http://members.xoom.com/JensSchu/ GPLRank: -2.61

No JensSchumi On Thu, 31 Aug 2000 17:02:34 -0400, "GTX_SlotCar" <[email hidden]> wrote: >Why, wouldn't it run in Safe mode? --------------------------------------------- LWFF Ball Bearing conversion at: http://members.xoom.com/JensSchu/ GPLRank: -2.61

In article <[email hidden]>, [email hidden] (JS) writes:

Quoted text (15 lines)

>You have to get in safe mode during reboot. >Since I'm too lazy to look up the proper keystroke, I reset during reboot. >The next boot will be in safe mode. > >JensSchumi > > >On Thu, 31 Aug 2000 18:29:51 GMT, "Pops" <[email hidden]> wrote: > >>Scenario: >> >>1. Bought a Voodoo 3 2000 >>2. Downloaded overclocker >>3. Overclocked from 143 to 173 in small increments ><snip>

F5 on boot, for future reference. Eldred -- Tiger Stadium R.I.P. 1912-1999 Homepage - http://www.umich.edu/~epickett GPL hcp. +50.77 Never argue with an idiot. He brings you down to his level, then beats you with experience... Remove SPAM-OFF to reply.

It boot a Win95/98 machine to safemode. SLG Red 86 Vet <[email hidden]> wrote: >>F5 on boot, for future reference. > >What does F5 at boot do? > (All spelling errors are intentional and are there to show new and improved ways of spelling old words. Grammatical errors are due to too many English classes/teachers)

Red 86 Vet wrote: > > >F5 on boot, for future reference. > > What does F5 at boot do? Safe mode. -- Chuck Kandler Windows--computing for the Unwashed Masses Registered Linux User #180746 http://counter.li.org

ah... thought that was F6..... <shrug> anyway, I knew one of them F keys did safe mode.... Maybe F6 is the menu or is that F8.... oh well... On Thu, 07 Sep 2000 21:27:07 GMT, Uncle Fester <[email hidden]> wrote:

Quoted text (8 lines)

>Red 86 Vet wrote: >> >> >F5 on boot, for future reference. >> >> What does F5 at boot do? > > >Safe mode.

On Thu, 07 Sep 2000 21:51:14 GMT, Red 86 Vet <[email hidden]> wrote: >ah... thought that was F6..... <shrug> anyway, I knew one of them F >keys did safe mode.... Maybe F6 is the menu or is that F8.... oh >well... F8 starts windows without loading your startup files. Handy for bypassing people who think putting a shortcut in their startup group for a password protected screensaver is 'security'. ~daxe

So easy??? Thx for the hint :-) JensSchumi On 07 Sep 2000 21:18:25 GMT, [email hidden] (EldredP) wrote: > >F5 on boot, for future reference. > >Eldred --------------------------------------------- LWFF Ball Bearing conversion at: http://members.xoom.com/JensSchu/ GPLRank: -2.61

In article <[email hidden]>, daxe <[email hidden]> writes:

Quoted text (10 lines)

>On Thu, 07 Sep 2000 21:51:14 GMT, Red 86 Vet ><[email hidden]> wrote: > >>ah... thought that was F6..... <shrug> anyway, I knew one of them F >>keys did safe mode.... Maybe F6 is the menu or is that F8.... oh >>well... > >F8 starts windows without loading your startup files. Handy for >bypassing people who think putting a shortcut in their startup group >for a password protected screensaver is 'security'.

No it doesn't - that just gives you a menu, and *one* of the options is safe mode. F5 does it without having to GO through that menu... Eldred -- Tiger Stadium R.I.P. 1912-1999 Homepage - http://www.umich.edu/~epickett GPL hcp. +50.77 Never argue with an idiot. He brings you down to his level, then beats you with experience... Remove SPAM-OFF to reply.

On 09 Sep 2000 17:15:42 GMT, [email hidden] (EldredP) wrote:

Quoted text (16 lines)

>In article <[email hidden]>, daxe ><[email hidden]> writes: > >>On Thu, 07 Sep 2000 21:51:14 GMT, Red 86 Vet >><[email hidden]> wrote: >> >>>ah... thought that was F6..... <shrug> anyway, I knew one of them F >>>keys did safe mode.... Maybe F6 is the menu or is that F8.... oh >>>well... >> >>F8 starts windows without loading your startup files. Handy for >>bypassing people who think putting a shortcut in their startup group >>for a password protected screensaver is 'security'. > >No it doesn't - that just gives you a menu, and *one* of the options is safe >mode. F5 does it without having to GO through that menu...

I had 'em backwards, then. Whoops! ~daxe

I believe that holding the Shift Key bypasses all startup files, too. -- Slot Tweaks & Reviews www.slottweak.com "daxe" <[email hidden]> wrote in message news:[email hidden]... > On 09 Sep 2000 17:15:42 GMT, [email hidden] (EldredP) wrote: > > >In article <[email hidden]>, daxe > ><[email hidden]> writes: > > > >>On Thu, 07 Sep 2000 21:51:14 GMT, Red 86 Vet > >><[email hidden]> wrote: > >> > >>>ah... thought that was F6..... <shrug> anyway, I knew one of them F > >>>keys did safe mode.... Maybe F6 is the menu or is that F8.... oh > >>>well... > >> > >>F8 starts windows without loading your startup files. Handy for > >>bypassing people who think putting a shortcut in their startup group > >>for a password protected screensaver is 'security'. > > > >No it doesn't - that just gives you a menu, and *one* of the options is safe > >mode. F5 does it without having to GO through that menu... > > I had 'em backwards, then. Whoops! > > ~daxe

In article <xxLx5.3375$[email hidden]>, "GTX_SlotCar" <[email hidden]> writes: >I believe that holding the Shift Key bypasses all startup files, too. > Sure, on a Macintosh....<g> Eldred -- Tiger Stadium R.I.P. 1912-1999 Homepage - http://www.umich.edu/~epickett GPL hcp. +49.67 Never argue with an idiot. He brings you down to his level, then beats you with experience... Remove SPAM-OFF to reply.

> Sure, on a Macintosh....<g>Heheh, it may at that. But seriously, holding the shift key while you're booting will run windows in safe mode. -- Slot Tweaks & Reviews www.slottweak.com