Hy Gedia,

i figured out, that with new kernel you dont nee dhc or hdb anymore..

it just works with sda…

thats what i did:

i updated my old HS3 (on kvm) to the new 4.0
the major change was the harddisk is now sda and no longer hdc
i use a suse11.3 64bit (know its not the newest).
created 4 partitions:
/dev/sda1               1         132     1060258+  82  Linux swap / Solaris
/dev/sda2             133        1177     8393962+  83  Linux
/dev/sda3            1178        1309     1060290    6  FAT16
/dev/sda4            1310        1441     1060290    6  FAT16

then i extracted the firmware file from experte 4 (zip) for HS3
(because i works with my old mac-address)
therefor i unpacked the inird with
gzip -dc ../INITRD | cpio -id
to a dir..

then i copied the hs dir to the rootpath of my linux
and when i started i needed to install some python-packages..
but first i copied all the python-dirs to my linux /usr/lib/python
there is a PIL dir which is needed..

then i can start it. With a script.

*****************************************
PYTHONPATH=/usr/lib/python/PIL
export PYTHONPATH
TZ=CET-1CEST,M3.5.0/2:00,M10.5.0/3:00
export TZ
hwclock –hctosys –utc
setserial /dev/ttyS0 autoconfig
setserial /dev/ttyS1 autoconfig

#only needed for serial transfer 1 time:
#/hs/bin/hs_main trans
#killall -9 python

/hs/bin/hs_main main
reboot
*********************
The communication for the first time I did with a nullmodem cable to windows8
The serialport on the new hs was ttys0…. It also changed…
Now it works fine…

on original HS4-hardware there are
15MB
110MB
870MB
870MB

all dos formatted, but the do something strange with turbodisk..
and then start it with loadlin to a ram -image. with busybox