I didn't press anything while the SE upgrade was taking place but I will say that after receiving the "SE Updated" message, I tried to reboot the Emax per the instructions but it hung trying to reboot to the floppy. I gave it about a minute or so to see if it would finish, but ultimately powered off and then back on and it booted to the se upgrade disk fine at which point I checked the os revision was indeed HD SE 1.1 leading me to believe the eeprom was successfully updated. But there's no harm in making a new floppy and trying the upgrade again.
Thank you guys again for all your knowledge and advice!
---In emax@yahoogroups.com, <jammie.emma@...> wrote :
here is one of teds bootable images unzip it load the image in the images folder inside emxp folders then choose emax1/2 images in emxp choose hd/cd images and choose restore image to hd its all in the emxp manual i have written this image and can confirm that it works just like the images i use you can also manage os images from this disk and save it to the os images folder
https://www.dropbox.com/s/3kufnae3obqqdml/EMAX1-1.EZ1.zip
the only other thing i can think of is that you botched the se upgrade did you press or touch any buttons when it was upgrading as this can brick the se upgradehttps://www.dropbox.com/s/3kufnae3obqqdml/EMAX1-1.EZ1.zip
On 1 July 2014 19:09, JAMIE logan <jammie.emma@...> wrote:are you creating a blank new image in emxp and adding the os image to the blank emax image and then are you using emxp to write that image to your hd
On 1 July 2014 17:00, Ted Summers djtbs1@... [emax] <emax@yahoogroups.com> wrote:-TNot sure if there is a factory reset to clear the parameter EEPROM....The SE update performs an update to the parameter EEPROM. Now, if it had written some bits to an incorrect location (IE, the SE update image itself was mucked up), then I guess it might be possible.Noting that if your EEPROM has bad values in it now in incorrect places, and update the SE again, it isn't going to fix the botched bits that are in locations that are not where the SE was supposed to update (does that make sense???).
Again- I've never seen this behavoir.On Tue, Jul 1, 2014 at 7:12 AM, xeelox@... [emax] <emax@yahoogroups.com> wrote:>>So what happens if you change that OS on the image to a non-Plus OS?
WARNING-------------------------------------------------------------EMXP only allows the installation of the Emax Plus OSon an EMAX-I HD/CD Image. Please select the Plus OS.Press any key to continue...This happens w/ versions 2.11.3 and 3.00. Did older EMXP versions allow different OS for HD images?I guess I could pull my last fully working drive and do a backup image in EMXP, but I'm still a tad reluctant to mess w/ my last drive until I know whether there's something I'm doing that's causing these issues.>>I have never seen the SE update go weird, but maybe yours has and needs redone….Was thinking along those lines last night. Bad or failed eprom update? FWIW 2 of my keyboards were SE from the factory and I can't boot the drives in those either, but it did all start the day I tried to update a non SE kybd to SE and then to Plus. Could a botched SE upgrade be to blame for failed HD formats, essentially rendering those drives unreadable/unusable by Emax?- Jim
---In emax@yahoogroups.com, <djtbs1@...> wrote :So what happens if you change that OS on the image to a non-Plus OS?I have never seen the SE update go weird, but maybe yours has and needs redone….-TOn Jun 30, 2014, at 9:10 PM, xeelox@... [emax] wrote:Ok, I figured out how to add an OS to an HD image in EMXP. So I made an image w/ the plus OS but it would not boot straight from the HD.
Every once in a while, booting from the floppy with the hard drive connected, it did get past the "Just a moment..." message and finally finish loading the OS from floppy, though it took a long time. Sadly I still get the "HD Catalog Error" whenever I attempt do do anything that requires the hard disk. But it is an interesting change in behavior. It's a small clue, though I don't know what to make of it yet.Jim