System Reboots

[zipdrive]

I'm having and issue with 1.3.7 (not an issue in 1.2.6). My system has a SB PCI 512 (I know its old) but it is not an issue in 1.2.6. Every time I click record, I get rebooted. I currently have tried using MS Sounder Mapper for both input and output and also SB as both input and output with the same result, however the only difference is instead fo 10 or 15 seconds before the reset, it happens immediately. This is obviously a system issue since I am not having this problem on a laptop with the same OS (both run XP sp3 and both use same Security software (F-Secure)). If anyone has some suggestions, I'm open to them. I think Audacity is awesome (with the exception of some random application crashes I've experienced in the stable version), I definitely think its more of what I need than what comes in Sound Forge (forget you sony!! ).

I noticed there was a post on a user having issues very similiar in 1.2.6 but it turned out to be a new driver that was installed for the sound card, thats not the case with me since the last update was in 2001 but its not a problem in the stable version and I am not open to buying a new sound card.

Thanks,
Zip

[steve]

See if you can record with "Windows Sound Recorder". That will give us a good starting place.

[zipdrive]

See if you can record with "Windows Sound Recorder". That will give us a good starting place.

As I explained in my original post, I can use (record in) 1.2.6 with no issues but for the sake of argument I did try sound recorder and I had no issues there either. There must be some hardware issue on this system the beta version does not like. It would have been nice to have a built-in crash log within Audacity whenever an issue arises, Event log doesn't give much info unless you guys want the minidump?

Thanks,
Zip

[kozikowski]

Thanks. Nobody ever reads the mini dump and I count myself in good company there.

How big is the hard drive and how much room do you have left? Is the system drive the only thing connected? USB drives? Thumb Drives?

How many red bars did you get when you defragmented? Did the error check go OK?

If you continue to get system dump problem like this you may have a bad memory stick. Do you fast boot the machine or do you let it sit there and count memory for a minute or two? Have you ever run a memory test?

This one is very well respected.

http://oca.microsoft.com/en/windiag.asp

Koz

[zipdrive]

Thanks. Nobody ever reads the mini dump and I count myself in good company there.

How big is the hard drive and how much room do you have left? Is the system drive the only thing connected? USB drives? Thumb Drives?

How many red bars did you get when you defragmented? Did the error check go OK?

If you continue to get system dump problem like this you may have a bad memory stick. Do you fast boot the machine or do you let it sit there and count memory for a minute or two? Have you ever run a memory test?

This one is very well respected.

http://oca.microsoft.com/en/windiag.asp

Koz

I think we're putting the cart before the horse here when we're only talking about one application being the problem. I don't have this issue with the stable (noticed I said stable) version along with the rest of the applications that I use. My memory is fine and I've checked it numerous times this year with MS's diag. tool. I have 2 SATA drives attached and the system drive has plenty of room (20 GB free). Besides this is a beta version and I was under the impression bugs needed to be reported I just wish the application produced a log during crashes.

Thanks for the info though.

Zip

[kozikowski]

<<<one application being the problem.>>>

I don't agree. A simple audio program should not cause the machine to reboot even if it is profoundly unstable.

"The application is not responding and will be closed. All other applications are unaffected." "The application has performed an illegal action and will be closed by Windows."

You have something the rest of us don't have. A brittle machine.

We more or less stopped paying attention to that silly Stable/Unstable thing a long time ago. There is no "stable" Audacity 1.2 for Mac/Intel/Leopard. The only Audacity left standing for new Macs is version 1.3.

Koz

[zipdrive]

I don't agree. A simple audio program should not cause the machine to reboot even if it is profoundly unstable.

Meaning you don't really know. :p

"The application is not responding and will be closed. All other applications are unaffected." "The application has performed an illegal action and will be closed by Windows."

This is irrelevant since I am not getting this message.

You have something the rest of us don't have. A brittle machine.

because of a specific application (in beta none the less), and I have a brittle machine? There is a reason why packages are in beta, to discover issues just like this. Do you rush to judgement on a regular basis?

We more or less stopped paying attention to that silly Stable/Unstable thing a long time ago.

Are you a contributing developer? I find that statement a little unsettling if you help develop this software, I'm hoping "No".

There is no "stable" Audacity 1.2 for Mac/Intel/Leopard. The only Audacity left standing for new Macs is version 1.3.

Using PC so this statement is irrelevant as well. PC != MAC & I now am guessing "No" on the previous statement.

[zipdrive]

You have something the rest of us don't have. A brittle machine.
Koz

Ur a mac user so your statement is unfounded. http://audacityteam.org/forum/viewtopic ... 15&t=10076

Don't interpret virtual with reality, you'll just confuse yourself.

[steve]

As I explained in my original post, I can use (record in) 1.2.6 with no issues but for the sake of argument I did try sound recorder and I had no issues there either.

From your initial post I could not tell if you used Audacity 1.2 on this machine 3 years ago, or yesterday. Without wanting to ask you to reinstall Audacity 1.2.6 I was wanting a quick confirmation about the ability of your system to record something (anything) today. Thanks for humouring me and checking it out.

Audacity uses portaudio to communicate with the computer sound system. Since Audacity 1.2.6 was created, portaudio has moved on by several versions. (It would not be practical for Audacity to stick with an obsolete version as this would cause more problems for more people using modern hardware and modern operating systems).

Unfortunately it sounds like there is probably a basic incompatibility between the current version of portaudio and your old sound card drivers. I can see no way round this issue - other than sticking with Audacity 1.2.6 for use with your SB PCI 512 and its 2001 drivers.

If your sound card is one of the less ancient SB PCI 512's then there is one possibility that may get you working, but it only applies to those that have the EMU10K1 chip. Perhaps you could check the model number of the card in case you have one of these. You will probably need to search the Creative Labs web-site for this information (and hope that they still have information going back that far).

[zipdrive]

As I explained in my original post, I can use (record in) 1.2.6 with no issues but for the sake of argument I did try sound recorder and I had no issues there either.

From your initial post I could not tell if you used Audacity 1.2 on this machine 3 years ago, or yesterday. Without wanting to ask you to reinstall Audacity 1.2.6 I was wanting a quick confirmation about the ability of your system to record something (anything) today. Thanks for humouring me and checking it out.

Audacity uses portaudio to communicate with the computer sound system. Since Audacity 1.2.6 was created, portaudio has moved on by several versions. (It would not be practical for Audacity to stick with an obsolete version as this would cause more problems for more people using modern hardware and modern operating systems).

Unfortunately it sounds like there is probably a basic incompatibility between the current version of portaudio and your old sound card drivers. I can see no way round this issue - other than sticking with Audacity 1.2.6 for use with your SB PCI 512 and its 2001 drivers.

If your sound card is one of the less ancient SB PCI 512's then there is one possibility that may get you working, but it only applies to those that have the EMU10K1 chip. Perhaps you could check the model number of the card in case you have one of these. You will probably need to search the Creative Labs web-site for this information (and hope that they still have information going back that far).

Thanks, I'll check that out. It's nice to know "brittle" isn't the final say so.