DragStrip® FAQ

The question you may have is printed in bold. Many questions with the same solution may be listed in a row.
The solution for the problem you may be having is printed in italics.
An explanation of your problem(s) and the solutions is printed in regular text to help you get to the root of the problem.

Questions and Answers

How do I stop a strip from reiconizing when I switch out of DragStrip?
There are several ways to do this.
1) Click the zoom box in the DragStrip title bar.
2) When the strip is Iconized, choose Uniconize from the Options menu.
Either of these will uniconize the strip and it will stay that way until you manually iconize it again, either by clicking the zoom box again or choosing Iconize from the Options menu.

DragStrip keeps running out of memory.
What operating system are you running?
How much RAM is allocated to DragStrip?
Are you running on a Macintosh with OS 7.5.2 or a beta of 7.5.3?
There is a memory leak in SizeWindow in Mac OS 7.5.2 and 7.5.3 that slowly but surely makes ANY application run out of memory if any window resizing is going on. Each resize loses a few K of RAM. This is especially noticeable in DragStrip because the Processes Strip resizes with every launch and quit of an application.
The update to full 7.5.3 corrects this. If you can't upgrade at the moment, these are a few ways to lessen the effects, though: Turn on the preference for "show only applications" in the Processes Strip preferences. This will stop the resize for all of the extensions that may be running at various times, and things like PrintMonitor won't pop up on the strip.
Allocate more RAM to DragStrip.

I just got DragStrip, and after installing, I'm prompted to either Install or Cancel to have DragStrip load on startup. No matter which one I choose, DragStrip bombs with a Type 11 error. To make matters worse, now everytime I restart, DragStrip tries to load (because I chose Install), then bombs, and I can't get anywhere.
What version of DragStrip did you buy? (Do a Get Info on the application.)
What Mac are you on?
PowerMacs (and Quadras/Centrises with PPC accelerator cards) require that a shared library called ObjectSupportLib be installed in the Extensions folder. Without that extension, DragStrip won't load.
Solutions:
Update to DragStrip 3.6, and the extension will be installed along with the new application. If you're on a Quadra with a card, make sure you start the installer with the Mac is running as a PPC, or the proper files won't be installed.
If it's an emergency, we'll e-mail you ObjectSupportLib. However, you should still upgrade to 3.6.

I keep getting a message saying that another person is using my serial number on the network, and DragStrip quits. No one else is running DragStrip.
Upgrade to version 3.0 or later. Network serial number checking has been removed.

DragStrip freezes up my Mac when I try to do PPP connections.
Download and run the DragStrip Fix immediately!

I'm on a PCI Mac, and DragStrip is crashing all the time.
What do you have on your strips? Are there any DS Additions or Control Strip Modules on there? If so, which ones? There is a problem with some of the DragStrip Additions and some Control Strip Modules. On non-PCI Macs, there are two separate control panels for Monitor and Sound. Some of our additions access these (i.e., Set Monitor Depth and Set Volume). PCI Macs running 7.5.2 have one control panel (which is actually an application) that combines the two - Sound&Displays. This control panel has a bug in it that causes DragStrip to crash. There are certain Control Strip Modules that do the same thing. Anything that tries to set volume, or bitdepth, is a candidate for a crash under 7.5.2. The system upgrade to 7.5.3 replaces Sound&Displays with Monitors&Sound. There is no longer a conflict with associated DragStrip Additions and Control Strip Modules.

Some Control Strip Modules crash my Mac.
Which ones? When in doubt, remove them all, and replace them one at a time. Anything written by SkidPerfect Software is suspect. Don't use them with DragStrip until we work out the conflicts with its author.

I'm on a PowerBook. DragStrip seems to wake it up when it's sleeping, and hits the disk a lot. I don't want my battery drained!
What do you have on your strips? There are certain "drawing additions" that do access the disk from time to time. These include the Show Memory Usage, Audio CD Player, Moon Phase, and Calendar DragStrip Additions, which rely on visual updates. There are Control Strip Modules that do the same thing (e.g., Battery). Put all of these additions and control strip modules on one strip, and keep it iconized or closed if you want the Powerbook to sleep normally.

I seem to get a lot of Type 11 errors, for no reason. I think DragStrip is the reason.
Are you running with Virtual Memory? There is actually a bug in VM that throws random memory errors, which is supposed to be fixed in 7.5.3. Try turning off VM for a few days and see if these errors persist.

I'm on a PCI Mac and I suddenly started getting a message saying that DragLib can't be found, and DragStrip won't launch. DragLib is installed, in the Extensions folder!
If you start with extensions off, does the message go away? This seems to be an indicator that there is something wrong with the OS, not DragStrip. We finally linked this to older versions of OpenTransport, and it seems to have cleared up with OT 1.1 running.

I'm running RAMDoubler 1.6 and DragStrip 2.0.1. Now, whenever I try to launch anything from DragStrip, the Mac freezes.
Upgrade to a later version of RAMDoubler. 1.6 had some "issues."