Where can I find the source code for the partition boot load

QNX Newsgroups (Archives) qdn.public.qnxrtp.embedded
21

ed1k,

I have disassembled part of what you sent, and it looks like you are writing
data out the same serial port after sending the initial message. Most
notedly, the dots that come out as the sectors are read in.

I would prefer NOT to see these come out.

Also, I am not sure, but it looks like there are a couple of data words in
the header that are blank (all 0’s) and they are used in a division
operation. Could this be a divide by 0 error causing it not to boot??

Or … mabe the fact that you are using int 13 function 2 and the qnx loader
uses int 13 function 42 (extended bios function). Possibly something
different about my drive?

Anyway… thanks for the good work so far.

Thanks,

John

“ed1k” <ed1k@humber.bay> wrote in message
news:MPG.1973ad1a6d3a35429896dd@inn.qnx.com…

In article <bec8qm$c77$> 1@inn.qnx.com> >, > john.h.eddy@lmco.com > says…
ed1k,

“OE removed access to the following unsafe attachments in your mail:
ipl-diskpc2-serial.dat”

I can see the attachment, but outlook won’t let me have it because it
has an
extension of .dat can you put it and/or source code in a tar / gzipped
file
and give it the extension of *.tgz. I am fairly sure that will not be
“screened” out by the e-mail server. Mabe I can get it from home?? I am
locked out of setting my security settings here at the office.


That attachments is really unsafe > :slight_smile: > Previously attached file had name
“ipl-diskpc2-serial”
without any extension. That .dat extension is a fantasy of your Outlook
Express. My newsreader
uses external encoding/decoding programs and I use uuencode/uudecode from
GNU sharutils 4.1, hence,
as I see attachment as a plain text with header, I’m sure about the name.
Here is attached john.tgz
which is tar-ed and gzip-ed ipl-diskpc2-serial.

ed1k



Thanks,

John

22

ed1k,

Ok, I tried this and it works.

I used the command:
dloader /dev/fd0 ./ipl-diskpc2-mrts
or
dloader /dev/hd0 ./ipl-diskpc2-mrts

… to write it to the disk, and it does as advertised.

Thanks Much,

John

“ed1k” <ed1k@humber.bay> wrote in message
news:MPG.1975056fad2bb13b9896de@inn.qnx.com…

In article <beejm0$3m8$> 1@inn.qnx.com> >, > john.h.eddy@lmco.com > says…

John,

Well, it is a good result > :slight_smile: > You saw the wrong size font because I forgot
to include font selection
sequence in string, sorry. Here is attached ‘ipl-diskpc2-ser’ and winzip
archive ‘john.zip’ which
include another copy of loader (for case of unsafe attachments filtering).
This time I put the
command “0x1f,0x28,0x67,0x40,0x02,0x02” in the greeting string, but in
order to save some space I
had to remove section outputting the dots during the boot process. So, it
won’t be so fun anymore.
Error messages about wrong image signature or disk IO error will still go
out through serial port.

It can’t continue booting if you used just dd like you did. dloader puts
disk drive parameters in
the header of loader. It depends on which device you are initializing.
Also, it is mandatory to give
a right name for the loader, because loaders name gives some important
information for dloader > :slight_smile: > I
guess, about is it primary or secondary loader. So,

dloader -v /dev/fd0 /boot/sys/ipl-diskpc2-serial

should work if you put ipl-diskpc2-serial (not mrts.ipl) into directory
/boot/sys/

ed1k

P.S. Don’t try disassemble my code, it could selfdestroy upon
disassembling > :slight_smile: > BTW, I sent you
loader by email also.



ed1k,

Ok, I got the attachment, and tried putting it on a floppy to test boot
on
the system.

I couldn’t get dloader or dinit to work, so did a “dd if=mrts.ipl
of=/dev/fd0 bs=512 count=1” and got it over to the floppy.

When it booted, I saw “starting system” in the wrong size font, and then
it
hung.
I tried copying it to the flash hard drive on the test box, and got the
same
results.

Here is what came out the port when I tried capturing it on boot up:
00 ff ff 1b 40 0c 1b 40 0c 20 53 54 41 52 54 49 4e 47 20 20 20 53 59 53
54
45 4d

I assume the 00 ff ff is noise on bootup or something like that. It
should
be:
1b 40 0c 1b 40 0c 1f 28 67 40 02 02 20 53 54 41 52 54 49 4e 47 20 20 20
53
59 53 54 45 4d

The missing string is the part that sets the font to larger size, so it
did
the right thing.

If I spatch mrts.ipl, I can see that the string is missing those bytes
in
the data section at the beginning of the file.

Can you send me the syntax you finally used to get dloader to work for
you.

Also… any idea why it won’t continue booting after the serial message
goes
out?

I tried disassembling the code with ndisasm -k2,0x29 mrts.ipl, but it
was a
bit hard to follow without comments.

Thanks,

John