Starship/win2k WS sp3/Fedex Server Manager

[MacolaHelp]

We've been using Starship for 1.5 years. This computer has been on line since April 03, Lexmark laser on local usb, standard starship eltron label printer on lpt1. Using low volume internet based fedex interface, we began to experience long delays on multiple package shipments using the repeat button, especially near end of day. Client upped to 1 gig RAM (celeron processor, tho, YUK!). No help. We purchased FSM so Starship would run locally, not over the internet. Performance improved immediately. 2 weeks after install, the first shipment of the day ran the cpu up to 100% utilization, forcing a hard power button shut down. Next time app opened, everything ran fine & did all day. We corrected this problem by increasing the swap file & optimizing background processing. All went fine for 3 days.

Our multi package shipment using repeat key has now revisited us, offending process is rate modifier. Took 30 minutes to get 12 shipping labels printed. No updates have been done to this machine. It runs macola, starship, fsm, norton av & a web app. Starship is v8.2 build 20040419. Only suggestion from V-Tech is to reregister ratemodcom & then to reinstall. Reinstalling SS is a major pain, necessitating touching 9 workstations that access the SS database & remapping everything, recreating audit labels & reports.

Really, nothing has changed on the machine. Grasping at straws, here . . . Norton updates? Anything else to try for cpu utilization problems?

 

[MacolaHelp]

We may have solved this today, actually. It probably had to do with the rate rules we loaded for internet shipping that no longer should be needed with FSM. Once removing the rate rules, everything improved. We have to wait for our fedex bill to find out if starship calculates correctly without a rate table.