When I open RealBand, I get a message "Your computer crashed last time you ran RealBand. Okay to restore all the default settings for a safe boot-up?"

Regardless of which option I select, the program stars. IF I open directly from the C;\Realband directoy in Admin mode, it is fine for a launch or three, but then reverts back to this.

If I answer "No" to the prompt, I appear to have my setting intact, though i have not looked in great detail. Is is reasonable to run this like this? Or who to contact for system help?

Thanks. I'd like to start using RB, but I have to be able to rely on it.

What is causing the crash message?

Do you close RB when done, or are you leaving it open all the time?
That message usually means it wasn't shut down properly. As long as you exit out of the program when done you should avoid the message.

I've seen that message, but only when the program was forced to shut down, like a power outage or something (not a proper shut down).

I always exit correctly, unless the app locks up, which has not happened with RB. That is my concern, there is no logical reason for the message. I initially temporarily stopped it by opening in admin mode - and thought at first that was the issue - but that is no longer "safe" either. So my questions are: how to fi it, and meanwhile, is it safe to work without fear of losing data...

Try: go to Control Panel > User > User Account Control Settings and turn that down or off and then try.
Is the User Account Administrator.

Thanks. I am already set to next-to none, and I'm reluctant to turn it completely off,e ven with Norton active.

So the question remain is it safe to run (best guesstimate, I won;t hold you responsible for any crashes) after telling the system to not reset my prefs? I don't know why it wouldn't be, but I don't know why I get the error, either...

Yes, it should be fine to tell it not to reset everything.

To try to fix it, rename RB.CFG and Realband.ini
This will cause them to rebuild and start over. However it also causes RB to reset to factory settings (which is what you are trying to avoid), and you may need to select your audio device, MIDI device, etc all over again.

Another option to try is to empty the RBERROR.LOG file. I'm just guessing, but the program may look at this file before the popup. Or save a copy of it first (for safety), then empty it and save it.
I just emptied mine and it had no ill effect. I right-clicked the file name, selected 'Open', then chose Notepad to open it with, deleted all text content (the error list), and saved it.

Since this is where RB keeps a list of past errors, it may be what is prompting the crash popup. Like I said, just a guess but it may be worth trying.

Thanks. As long as I am not going to damage the prog, the system or the data, I'll try anything once.

And resetting to factory is fine - once, for effect. It's just when it is needed every other launch...

Tried it, got the error message, letit reset. Ran for awhile fine, when I saved the work file it crashed... Work continues apace...

May have a rogue plugin in use or a corrupt file. Hard to say.
I can't think of much else to suggest.

Something else to try right click on Realband folder > Properties > General Tab > "Attributes" take off of Read Only if on it > Apply > All Sub-directories

solidrock, I believe you have nailed it. ANd when I uncheck it, as soon as I close the window, it goes back to Read-Only. Even though I have admin privileges, it doen't stay. Got to remember how ti fix that.

But I DO believe you have hit the nail square on the thumb. Thanks.

So I have changed the attribute, the command line says it is changed, the windows display does not agree. We'll see who wins...

Hi David,

As rharv and Solidrock have suggested, it sounds like Realband cannot write the necessary files when it exits.

When you say you run the program as administrator, could you elaborate a little more on that? I was always under the impression that Windows didn't let people simply log in as administrators - working as admin was a bit more convoluted than that.

Have you tried right-clicking the icon (or Start menu item) you used to start RB and then setting the shortcut to "Administrator"? Also, have you installed the latest update?

Regards,
Noel

Latest update installed. When you right-click on the RB icon in its folder, (and your User has Admin privileges, as I always do) there is an option to Open as Administrator" which brings up a dialog "OK To Run..."

So far, since fixing the folder at Command Line, the Command line now says the Read-Only attribute is OFF, but Windows still shows it ON. I have no idea how to reslove that dichotomy.

And I just launched RB and got the same Crash message. I am reasonably confident that resolving the folder attribs will resolve the problem, I just haven't found a way to make it happen yet.

David,

What folder/directory do you have Realband in? Is it off the "Program Files" directory?

Noel

That's normal it goes back to say Read Only but it's not, I don't think that is your problem if it's still crashing.
Can you just rename the Realband folder Realband-old and then install it again and when it is working make a copy of the working folder Realband-works so you have a backup.
You can also ask PG to get on Teamviewer if you install it.

Here is a Take Ownership right click menu option for Win7 but I don't think that's the problem.
TakeFileOwnershipWin7.zip

It does not appear to actually BE crashing, it appears to exit normally. But I can try a re-install.

I'm not aware of Teamviewer. Let's see how try two works. Thaks.

There are many ways to let support make adjustments to your machine.
Teamviewer
JoinMe
GoTo

There's another we use often, but can't remember it.
Dang sometimers

Anyway, they may ask to use any number of methods, I'd likely ask them what to install first. Most install pretty quickly. They may not even need to take control.
That way you don't end up with un-needed remote access type software installed.
Why install unless needed?

OK, reinstalled, first time opened as admin, set up and closed fine. Next opening worked great. Closed it, ran some other stuff for awhile, re-opened and got the Crash message. Guess I'll continue to use BIAB as my primary for this, and RB for multi-riffs when available or needed.

Did you try it with the UAC off ?

What is the Audio set to MME or ASIO, what Midi Synth is it set to in Midi Devices.
Don't give up on it, play around with different settings in Audio Preferences and Midi Devices, you will get it going !

Get off the net and try it with Norton disabled also.

Does it crash when you opened a song that you made in BIAB or without opening any song ?

This machine has had USB issues since purchase - my audio/midi interfaces regularly lose contact (AudioBox currently runs usually, but my Focusrite 8i6 blew out a USB port and will no longer even be recognized by the box (Dell XPS8700, supposedly a good machine...)

Midi devices currently again Audiobox and Coyote. Don't have a lot of optiona but a bunch of VSTi-Trillian, JABB, Lounge Lizard, Kontakt, etc. etc.

When I have time, i guess I'll try the support remote options, for now it's trial and error - mostly error.

Thanks.

If you have USB drop outs make sure you are using the rear ports on the motherboard and not the front, as the front usually just have thin wires going to the motherboard.
Good luck.

I now have the 2015 upgraded upgrade (build 411 BiaB) and have the same issues with reported "crashes."

It does not seem to actually impact anything beyond the settings, all the parts of the progam I have used work fine. But I cannot trust it, so I will be contacting tech support as soon as I have the time. Thanks for the help.

I hate to state the obvious, but if your computer has some issues like USB struggles, and such this may be a computer problem, not an RB problem. Very interesting read, I had that issue, somewhat different, but still crashed. My system was slowly going down.

I have one port that is odwn and I don't use it, the others report no problems. Dell is pretty solid in my experience, it may be a hardware thing, but probably more of the old mobo-chipset/interface/software trilogy of horrors. No one isolatable entity is the issue, just certain combos don't play well. I am having no problems running RB, only the occasional boot "crash," so I don't need to get super-aggressive with it. At this time. I'm just working more in BiaB before I transfer, if need be.

David,



The #411 build for BIAB does not directly impact on RB. Realband has its own updates. They can be accessed at the link below ...

http://www.pgmusic.com/support.realband.htm

It's build #2 that you need. You can check this under "HELP | ABOUT REALBAND", If build #2 has been installed, it will be in brackets after the version: e.g. 2015(2).

Regards,
Noel