Displaying 3 results from an estimated 3 matches for "abort_check".
2010 Sep 14
0
Handling error scenarios in the core
...o enter_command. Should it do
something based on ONERROR?
2) core/comboot.inc: comboot_bogus_tail and comboot_too_large go to
enter_command. Again, use ONERROR?
There may be more that I'm missing. I know bad_implicit/bad_kernel
and error_or_command (from abort_load) already use it. I know
abort_check (executed with user input) does not but this one make a
lot of sense as it's not a system error.
3) core/ui.inc and core/abort.inc: bad_implicit/bad_kernel is silent
if there's an ONERROR but any other function that calls abort_load is
not. Is this the desired behavior?
--
-Gene
2003 Dec 27
0
2 disks boot patch
...jmp abort_load
+; begin - freddy77
+change_disk:
+ mov si, change_disk_msg
+ call cwritestr
+ xor ax, ax
+ int 16h
+ call load_fat
+ ret
+; end - freddy77
+
initrd_end:
nk_noinitrd:
;
; Abandon hope, ye that enter here! We do no longer permit aborts. ;
call abort_check ; Last chance!!
mov si,ready_msg
call cwritestr
2003 Dec 27
0
FW: 2 disks boot patch
...jmp abort_load
+; begin - freddy77
+change_disk:
+ mov si, change_disk_msg
+ call cwritestr
+ xor ax, ax
+ int 16h
+ call load_fat
+ ret
+; end - freddy77
+
initrd_end:
nk_noinitrd:
;
; Abandon hope, ye that enter here! We do no longer permit aborts. ;
call abort_check ; Last chance!!
mov si,ready_msg
call cwritestr