\"out of space\" on device on load
J.Luszczek
Posts: 159
I've got a few random \"out of space\" messages while loading a system recently.
Some of the devices are pretty stubborn with it, while others come and go.
Even a Blu-120 (no DSP to run whatsoever) and Blu-10 (one page with 3 controls on it) will insist that they are out of space and refuse to load.
Another computer might load all devices with no problems, but mine will consistently throw up this error. I can boot in to Windows XP or Windows 7, but I get the same error regardless.
What might be the cause of this?
We are talking a system with a total of 12 devices, of which 5 are Blu-160, 1 Blu-10 and 6 are Blu-120's.
Some of the devices are pretty stubborn with it, while others come and go.
Even a Blu-120 (no DSP to run whatsoever) and Blu-10 (one page with 3 controls on it) will insist that they are out of space and refuse to load.
Another computer might load all devices with no problems, but mine will consistently throw up this error. I can boot in to Windows XP or Windows 7, but I get the same error regardless.
What might be the cause of this?
We are talking a system with a total of 12 devices, of which 5 are Blu-160, 1 Blu-10 and 6 are Blu-120's.
0
Comments
To turn off this unsafe automatic preference:
* Click on the TOOLS menu
* Select APPLICATION PREFERENCES
* Click the FILE tab
* Find the drop-down list that says either YES or PROMPT and change it to NO
To delete the design file from the device network, click on the FILE menu and select \"Remove Designs From Device Network\".
If this eliminates your symptoms, then the problem was the fact that saving to the device network uses the \"extra\" memory in the device. Unfortunately, the automatic save to device network happens BEFORE you load the device, so you end up filling all of the \"extra\" space based on the requirements of whatever design file you loaded last. If the current design file needs more memory to run, then you're out of luck and you get the error message.
The second possibility is that you've had lots and lots of MSWindows crashes and you now have a bunch of junk data stored in the DSP. To fix that:
* telnet to the device using its IP address
* username = bssaudio
* password = monkey
(if you're using box security, then the password is your box password)
* run the command \"purgexml\"
* run the command \"formatflash\"
* run the command \"reboot\"
The device will be reset to a completely factory fresh state. Set the name, load your file, and you should be good to go.
If that STILL doesn't fix it, then you've probably got a hardware issue. Also, it could be a problem with the NIC on your computer. You said \"another computer might load all devices with no problems\", but I don't know what that means. If might means will, then it could definitely be your NIC. If might means sometimes, then it's not the computer.
Dan
I tried clearing the designs from devices, bu that didn't help.
I suspected a problem with my NIC, because another laptop could load the file in the boxes with no problems. I looked for newer drivers for it and found an update. After that I have not run into the out of space error and my going on line seems to be much faster, but I have not tried yet to load every one of the 10 London systems I have here, including the ones that gave me trouble in the past.
But, this out of space on device has popped out on mine and another co-worker's machine. He got through on second or third try, I got stuck.
Third laptop has not run into this problem yet. So I suspect there is some change to the networking side of London software that causes problems with certain NICs.
Some things I learned:
Updating firmware DOES NOT erase project file stored on flash. So Bootloader will not set unit back to Factory settings. You have to:
* telnet to the device using its IP address
* username = bssaudio
* password = monkey
(if you're using box security, then the password is your box password)
* run the command \"purgexml\"
* run the command \"formatflash\"
* run the command \"reboot\"
(by the way, BootLoader is an app located in Help/Run Utility...)
This has been my good deed for the day.
Thank you.