I'm having some problems updating to the new bios300. I put the files in the su1.zip arhive in a folder on my sprinter, and run bios300.exe. It starts and show me a pink/green screen with three progress bars. But the program exits when the verify bar has reached its end. So there's no update of the bios. Anybody know whats wrong?

FlashROM Writer (the program with a pink/green screen and three progress bars) has four steps of work.

1 step - Verify. Checking of integrity of the BIOS300.EXE file. Program work will be aborted if check was finished not successfully.

2 step - Erase. Erasing of old information in the FlashROM chip.

3 step - Write. Writing a new information into the FlashROM chip.

4 step - Verify. Checking of check sum of new information in the FlashROM chip.
Program will print error message if check was finished not successfully. Restart of computer means a success of update.

So, David , in your case, program work was aborted after first step. It means - BIOS300.EXE file was copied to your disk with errors.
Try to copy the program to your disk by another floppy disk again.








---
PETERS PLUS LTD

Now that I remember, I had exactly the same problem. The BIOS updater from SU#1 aborted with no apparent reason after completing a Verify step; I assumed it was a bad download of SU#1, and I had a copy of BIOS300.ZIP handy, so I tested it out: It worked fine.

Maybe -just maybe- there's something bad with the BIOS300.EXE in SU#1, but the one in BIOS300.ZIP seems to be OK. Of course the EXE in SU#1 could be fine and the site had just two bad downloads, but... Who knows? Other than that, the rest of updates from SU#1 were OK.

Bottom line is: It wold be a great idea to check the BIOS300.EXE in SU#1...

Marcelo.
----------------------------------
Speccy rules, its staff is Sprinter.

We can't say about bad download as cause, because successful extracting of SU1.ZIP contents means its integrity. And there are no differences between BIOS300.EXE files from SU1.ZIP and BIOS300.ZIP.
But any way, BIOS300.EXE file from SU1.ZIP was downloaded from the our website and tested. It work correctly. So, the cause is not correct file copy from floppy disk by Flex Navigator. It's a pity, but Flex Navigator not use DSS messages about disk read errors. Please, use well-read floppy disk only!
We hope, software support of "Sprinter<->PC" link (which will be created this month) will help solution of this problem. But correct usage DSS messages about disk errors will be done in future. In a new file manager, may be, or in a new version of Flex Navigator.

---
PETERS PLUS LTD