| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
I used to be able to use WRITEBOOT to specify files quite easily
for a floppy to boot from, but I dont seem to be able to get
it to run any longer. It says FILE NOT FOUND (after asking
for the VBN of the code). It seems to do a directory search
of SYS$SYSTEM (even though the boot file is on a floppy
on another drive) before failing.
Can anyone save me the effort of searching through the microfiche
to sort this out ?
Also does anyone know how I can put a vaxeln .SYS file that was
generated for a remote load onto a disk (for booting). It looks
like there is something missing. Is it possible to patch it in ?
I dont have access to the source or .OBJ files.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 228.1 | booting ELN from floopy | DRFIX::RAUHALA | Ken | Mon Apr 07 1986 18:02 | 16 |
If a ELN .SYS file was EBUILD't for remote booting, I don't know details needed to convert it so it can boot from disk. However even if you don't have the source or .OBJ's, but you do have the .EXE files that were used to build it, you can add characteristic/boot_method=disk in the .DAT file and run it thru EBUILD again to create a disk bootable file. Oh, you have to give it a node name (number) also. Then $ COPY the_new_file FLOOPY:[SYS0.SYSEXE]SYSBOOT.EXE/CONTIGUOUS $ DISMOUNT FLOOPY: Or use the ELN$:COPYSYS.COM procedure. Then boot from the floopy and ELN comes up. At least that's what I do. | |||||
| 228.2 | Looking for SYS$SYSTEM:BOOTBLOCK | CLT::COWAN | Ken Cowan, 381-2198 | Wed Apr 09 1986 11:37 | 10 |
I believe WRITEBOOT is looking for SYS$SYSTEM:BOOTBLOCK.EXE. It
searches the specified disk for the file you specify, and puts the
logical or virtual block number as the first or second longword of
block block and copies BOOTBLOCK.EXE to the boot block of the bootable
disk.
I'm not sure how you were using WRITEBOOT. Does this help or
confuse the issue?
KC
| |||||