Is there already a floppy disk in the FDD, half-digested or not? If holding down the mouse-button at startup does not disgorge a floppy disk, using the paperclip magic wand in the eject-hole should do the trick. Either that or your FDD is in rigor mortis.
The 0003 tells you, in addition to the SE's having a PITB (where B here means belly), that it flunked its byte-write memory test, and the 1000 identifies the bad chip (not card). 'Bad' here could mean the seating or the socket or the card's edge-connector. You need some canned air to blow out the RAM sockets, one or two sets of paired RAM cards, and a pencil-eraser to clean the edge-connectors.
Option at start does indeed invoke a choice of startup volume, but when the choice is one at most I have no idea where that will get you. Your description of your hardware problems makes your software troubles irrelevant for the moment. Getting to raster (grey screen) followed by black screen and swearwords about its RAM is your first hurdle to pass.
de
The 0003 tells you, in addition to the SE's having a PITB (where B here means belly), that it flunked its byte-write memory test, and the 1000 identifies the bad chip (not card). 'Bad' here could mean the seating or the socket or the card's edge-connector. You need some canned air to blow out the RAM sockets, one or two sets of paired RAM cards, and a pencil-eraser to clean the edge-connectors.
Option at start does indeed invoke a choice of startup volume, but when the choice is one at most I have no idea where that will get you. Your description of your hardware problems makes your software troubles irrelevant for the moment. Getting to raster (grey screen) followed by black screen and swearwords about its RAM is your first hurdle to pass.
de