A3000 speed problem.

[glitch]

You have added:

CPU >NIL: FastROM Cache Burst

to your startup-sequence right?

If not, reboot and try your becncmarks again.

-G

[glitch]

Sure, right after the setpatch and version command lines.

I've got more ZIPs if you're interested.  I'll have to go and look at them to see what type they are though.

Good luck!

-G

[glitch]

Hi,

     I've got eight ( ZIPs left.  They're Toshiba TC514258AZ-80 if you're interested.

-G

[glitch]

Hi,

    $5 for the ZIPs and shipping is fine by me. PMail me for more on that...

    As for your startup-sequence, it should be something like this:

----------------------------------------
C:SetPatch QUIET
Version >NIL:
FailAt 21
Cd c:
Addbuffers >NIL: DF0: 32
CPU >NIL: FastROM Cache Burst
MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Mount >NIL: DEVS:DOSDrivers/~(#?.info)
Resident >NIL: C:Execute PURE
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart
IPrefs
Path >NIL: RAM: C: C:BIN SYS:System S: SYS:Prefs SYS:Tools
Execute S:User-Startup
LoadWB -debug
EndCLI >NIL:
-------------------------------

Backup (rename) your existing starup-sequence (in case it doesn't like something here) and copy and paste this one into a new startup-sequence file and give it a shot.

If I see a large mushroom cloud from the east, I'll know what happened!

Good luck!

-G

[glitch]

Cool!  When OS3.1 is installed (or 3.9 or whatever) it should create a brand new startup-sequence and overwrite the one you just made.  As a rule, I always add the CPU line to any machine I have worked on - and test it for a while to see how it works.  Some machines don't like the "burst" command due to other hardware they may have installed.

Regardless, have fun!

-G