Hi,

I am a long term user of all PG Music products and a frequent reader of the forums.

I always work out my issues where I can.

This issue I believe should be addressed (unless there is a work around that I am not aware off)

That is I use external sound-card with BIAB, Realband, PTW.

All are the latest and greatest versions.

I shutdown after using BIAB and next time I want to use it and If I don't have my external soundcard hookup up I get Access Violation in Module rDaw1046.dll plug it back in and all is fine.

Now if i go somewhere and forget my soundcard (which can happen, we are human) and use an alternative soundcard, I can't even open BIAB due to access violation to change drivers/soundcard.

Or if (most likely case) I simply want to open BIAB to enter songs or fiddle and don't have my soundcard in it crashes (Access Violation)

Can BIAB be open to default drivers if it detects soundcard not available (and why not)

Thanks
Lionel

Hi Lionel,

To help try and solve your problem, it would be useful to know the answers to the following questions.

1. What is your operating system (Win 7, Vista, etc.)?

2. Is your operating system 32-bit or 64-bit?

3. What version of BIAB are you using?

4. What directory is BIAB in (e.g. C:\program files\bb, c\bb, etc.)?

5. Do you run BIAB from the computer's internal hard drive?

Regards,
Noel

Hi Noel,

Win 7 64 bit.

The latest and greatest makes it 2012 latest update

Directory is D:\ Drive not root drive C:\

Yes it is internal drive

Thanks
Lionel

Lionel,

That's a curious problem that you have. When my system has not always had the soundcard, BIAB used to tell me that the driver couldn't be found but it still opened up and I needed to reset the MIDI output. This was before 2012, though. I haven't been in a position to discover if this is true of 2012.

It is possible to force BIAB to open by going for the ultimate factory reset. To do this, rename the files "intrface.bbw" (not spelling - it is NOT "intErface") and "mysetup.dk" in your BB folder. I usually rename them to "intrface.bbw.old" and "mysetup.dk.old".

Doing this effectively stops BIAB from seeing the setup files and it will create new ones. Then, when you return to where the soundcard is, you can rename the newly created files and then remove the ".old" ending from the previous one. This will restore your system to its previous state.

Before doing the above, though, I'd try a full factory reset and see if that makes any difference.

One other question ...

In you MIDI set up, do you have "Microsoft MIDI Mapper" selected as output? There have been many posts indicating that this has created problems and that changing to "Microsoft GS Wavetable" solves those problems. Such problems seem to occur even though the driver might not be being used because VXT/DXi is activated.

Hope these thoughts help,
Noel

Quote:

---

Hi Noel,

Win 7 64 bit.

The latest and greatest makes it 2012 latest update

Directory is D:\ Drive not root drive C:\

Yes it is internal drive

Thanks
Lionel

---

Hi Lionel,

This is strange behavior that I have not yet seen.

*Have you perchance installed bb to the Programs folder? With your OS, that is not the best place to install the program, as there are volatile files that bb must be able to write to when opening and closing and your OS doesn't like that.

*There is a possibility that Uaser Account Control (UAC) may be blockin things here also. UAC should be turned OFF for use with BiaB.

*Have you perhaps *disabled* the onboard sound in bios or the like?

There is a way to open BiaB when you are caught without whatever your aftermarket sound device happens to be -- go inside the bb folder and locate a file named, "intrface.bbw" and move it OUT of the bb folder. Then start up Band in a Box. The progam should go through the soundcard and MIDI drier wizard like it did when firast installed, giving you the chance to select the onboard sound.


--Mac