I got several times system failure during booting/installation with the content the processor's registers printed on da screen recently while trying to install by booting with bare.i/bareacpi.i diskett.

Any one else experienced that ?

Spec:
asus tx97-e, IDE ibm/maxtor 4 gb HD (LBA mode)..

i'm having problems trying to decifer exactly what your trying to get across ....
are you getting a successful boot with errors during the boot ?
or is the boot just failing at some point ?

and are you able to post the errors you are receiving ?

I got 1 or 2 times succesfull boot, but when I tried setup it goes woes LIKE kernel error with those CPU register printed on screen.

But most time even often failed to boot bare.i n booting with bareacpi.i failed not predictable, sometime ater inserting install.1 sometime even in the middle of booting bareacpi.i after entering "ramdisk hdd=ide-scsi" ..

I installed a usb 1.1 controller on mobo, but it has been took off from mobo. Several modification on BIOS setting also, reset back still a little modification that "I don't think responsible.

The purpose of the post is to get confirmation whether someone got the similar problem with bare.i bareacpi.i, I almost can not remember to have such errors with previous bare.i of 01-DEC-2003 ??

It was my mistakes, I used fdformat to format all the disketts, that is a little bit harmless, but I used stfdprm to set other parameter 1440/720 for fdformat (see also /etc/fdprm, it is of 1994) ! So fdformat must be using that bad parameter to format the disketts. That could be the cause of the mal/failing to boot the fdformat formatted disketts.

Now after reformated the disketts with dos-format, I can boot with them bare.i, install.1, install.2, null problemo..
But one prblem still exists, the network.dsk disk of few days ago that i got from slacksite was still of DEC-2003 n used kernel 2.4.23. Those newer bare.i, install.{1,2} are compiled with 2.4.24, so when I used that old network-disk to try to load the 8139too module, it failed to load somehow.

I then stole a network.dsk form zuuls.slw.. current-tree, it is newer (JAN-2004), I got it also to load 8139too succesfully, but somehow when I try to mount an exported nfs directory, it said:

Portmap: not registered ... (like that exported 10.x.y.z:/path/to/current-tree not exported or unvisible to him), n I couldn't find any /etc/rc.d/rc.portmap script somewhere ?

I even tried to force setup to use that exported dir but it failed with the same error. I can ping from the installing host to the exporting host, no error, 100% answered/replied, any clue ?

----
N, u know wut ?

Slackware is definitive the winner, undoubtfully ..

N

Winner take all !!