BitBangerUSA

which registry do i change? in the prefix folder there are many options..... ah... re-read the instructions. there's one one registry - although it contain LOTS of settings... and i don't believe anyone mentioned a 'prefix folder' in the post... the key you want to change was very specifically detailed - if you are *even a bit unsure* about finding the right one, you are probably better off not even attempting the change - get the wrong thing and you may seriously regret it.

outlook or outlook express? big difference... got MS Office? older version - make sure the silly auto document update isn't set to the default of every 2-hours. don't know about newer versions of MS Office. you fixed it before but don't remember... start a text file to record changes to your system - pen and paper or a text file can be a handy mechanism for expanding your memory (gray-matter type, not silicon).

nice tip - thanks.

'Does anybody else think this is unusual???' unusual? - no. looks to me like just another company trying to make some easy bucks providing a 'service' that can be obtained cheaper (or for free) by the mobo maker. the $70 is to me, excessive - as is the $30 for the 'download form'. as bios code is not something that just anyone can code, i would wonder where and if this ESupport outfit has obtained the rights to be selling this 'service' or code. sounds like a Big Red Flag to me. granted, some users may just not want to (or be able to) deal with 'doing it themselves' regardless of how much effo

as noted, some checking on the user input is always a good idea unless the program is being done as an exercise or as a 'quick-and-dirty'. you should try to NEVER assume that the user of your program will enter the data you expect. somewhere, sometime, some user is guaranteed to find a way to confuse your code. most compilers provide some means of controlling what is emitted by the compiler, such as debug info. some even provide a means of using run-time calls to libraries, rather than rolling in library code into a stand-alone executable, resulting in a smaller exe file - but then the program

i didn't find much on this mobo with google... if you can post a link to where you looked, i'll visit and see if i can direct you to a particular bios update...

'almost completely useless and lame programming skill i took on was to program my calculator' well, that's easily argued both for and against... for: you may need to shoe-horn your code and data into a small memory space - such skill might be handy programming in an embedded environment, even today. not all computers are PC-types with gobs of RAM and hard drive space available. against: if you code for MS, you might not care about how bloated your program is... well, shut my mouth! - no i's not a MS programmer.

did you check to see if the mobo maker has a bios upgrade? the better mobo maker's have FREE bios updates - along with the info on what problems have been fixed. btw - i run a mobo that's about 5 year old now and have never updated the bios - but i have the program and update file(s) just in case. as noted, unless you KNOW that a bios update will fix a particular problem (AND you are having that problem) it's best to leave the bios as-is. i understand that some of the newer mobo's have some 'safety' features in case the bios flash procedure fails - but likely you don't have that kind... anyway

gee, i have the same problem as your friend... yes, a PS can degrade gradually and result in power-up problems. i spent about 90 minutes getting mine back up - removed un-necessary cards, fans, drives, etc. during which i verified that the power switch was not at fault, video card was still good, etc. after getting the system to boot, i've just left it on all the time and have monitored the PS voltages (both with a meter and with software) and the PS is solid - once it starts. no crashes on the computer either. still running fine after about a week like that. not that this means your friend de

'Does anyone have any idea why this is happening in the first place?' a couple of possibles... 1. change in screen resolution or having a virtual screen management scheme with your video card. 2. bad programming - this was not uncommon in the early days of windows programming - but would not seem to be the issue with the programs you mentioned (although some (actually a lot) of the code for MS Calc is ancient). looks like CurlingSteve hit your nail on the head, nerelda.

lance corporal murphy is correct.

ooohhh... a programming section. nice to see! don't know who jeff is (i've been gone a while) but i know who B is. i'll add my Thanks To Whoever.

what have you done to try to get into the bios? most systems put up a text message about what key to hit during the pre-windows boot process. perhaps your bios is password protected, in which case, you will need to clear the cmos settings by either using the bios reset jumper or pulling the cmos battery for about twenty minutes. all you described about using PM 8 and then lack of booting from hard drive is normal. you will need to set the bios to boot from the cd so you can run the XP install.

hey - saw that some idiot on another board gave a link for how to check if IAA is installed on a system, ignoring the fact the this problem is occurring on an AMD system. duh! some people!

but what are the questions? problems with coding a while/wend loop - no details given.