how to convert physical Tru64 v4.0 d to virtual

Hallo

I have some special tru64 commercial midecal application that can`t be installed in an usuall tru64, but only on special tru64 from the company, and the special tru64 can`t be installed on usuall alpha worksation but on special alpha worksation from the company.

The tru64 and the main midecal applications was from "picker" in one CD, I tested to install the tru64 in "personal alpha" emulater, it boots from CD but tell me that this tru64 kernel can`t be installed exept in an alpha machine from picker named "odyssey FX" that I have.

The system is insalled in 2 GB disk ided 2 partitions:

/ 64 MB, contains the tru64 kernel, it`s a spicail kernel
/img0 contains the spicial applications and data

So... I think of making a virtual image of the whole tru64 system on a vitual disk, and to make network between this virtual tru64 and a physical computer of a Gamma Camera to get midecal images.

Is this possible??

Please help me for I well tell you the results.

Hi,

I see this has been discussed on the HP ITRC forum as well :

forums13.itrc.hp.com/service/forums/ques....do?threadId=1419402

Over there, the question was raised as to how 'odyssey FX' differs from a 'standard' Alpha ? Also asked was have you contacted Phillips about how to move to a new (emulated) platform ?

> I think of making a virtual image of the whole
>Tru64 system on a vitual disk, and to make network
>between this virtual tru64 and a physical computer of a
>Gamma Camera to get medical images.
>
> Is this possible??

Maybe.

You should be able to copy the boot disk of your Alpha using dd. You will need to dd the 'c' partition in order to copy the entire physical volume including the boot sectors and disk label. You will need somewhere to 'capture the dd output, and then copy/ftp/export/move the file to the Windows system on which you will run FreeAXP. If you only have 1 disk in your Alpha, you may need to use NFS to another Un*x (or Windows) system to provide the neccessary disk space.

The sequence might look like this :

ofx # mount bigsys:/bigspace /mnt
ofx # dd if=/dev/rz0c of=/mnt/OFX.img bs=128k

bigsys # ftp /mnt/OFX.img -> windows machine

start FreeAXP wizard, set OFX.img as DKA0 (ie. rz0)
start FreeAXP, boot DKA0

(in the above, ofx is the odessy system, bigsys is an NFS server, and rz0 is your oddessy root disk, your actual disk name may be different - 'scu sho edt' and mount or showfdmn, will reveal which disk is the root disk)

Then post us the results in the forum.

Also, can you tell us more about 'odessey FX' ?
Can you post a sys_check -all output ? or the boot messages ? to help us see what is unique about the platform.

John M

>can you tell us more about 'odessey FX' ?
Can you post a sys_check -all output ? or the boot messages ?

Yes, to my pleasure.

I prefere to try copying the system myself to freeAXP before asking Philips, for it seems difficult for them to deal with such old systems.

I have read your reply, but not undrestand all thing, for english isn`t my own language or for Im not tru64 expert user, Im newuser, but somehow old user of "Odyssey FX" imager.

Today I have managed to share and mount an windows folder by NFS in tru64, so I have new 10 GB free space.

Is OFX.img will contain both two partitions / ,/img0, and swap partition?

Please,I have undertood all things expet:

>'scu sho edt' and mount or showfdmn, will reveal which disk is the root disk).

>Can you post a sys_check -all output ?

How?

>or the boot messages ?

can`t write down them, they are faster than I could.

With very thanks.<hr>

Im not sure about the name of disk device in my alpha.

scu sho edt

CAM Equipment Device Table (EDT) Information:

Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W

---

---

---

---

---

---

---
0 0 0 Direct SCSI-2 DEC RZ28D (C) DEC 0008 N
0 4 0 CD-ROM SCSI-2 DEC RRD46 (C) DEC 0557 N
0 6 0 Sequential SCSI-2 TANDBERG TDC 4100 =05O N

I tried dd if =dev/RZ28D of=/mnt/OdysseyFX.img bs=128k

/dev/RZ28D: No such file or directory

try

ls /dev


MAKEDEV prf rmo0c.FX729 rrz29e rz17c sad
MAKEDEV.log printer rmt0a rrz29f rz17d snmpinfo
SYSV_PTY ptm rmt0h rrz29g rz17e streams
acqproc0 ptmx rmt0l rrz29h rz17f tmp
acqproc1 ptmx_bsd rmt0m rrz30a rz17g tty
acqproc2 pts rmt1a rrz30b rz17h tty00
acqproc3 ptyp0 rmt1h rrz30c rz21a tty01
audit ptyp1 rmt1l rrz30d rz21b tty02
binlogdmb ptyp2 rmt1m rrz30e rz21c ttyp0
cam ptyp3 rmt1x rrz30f rz21d ttyp1
cdrom ptyp4 rrz0a rrz30g rz21e ttyp2
console ptyp5 rrz0b rrz30h rz21f ttyp3
fd0a ptyp6 rrz0c rrz4a rz21g ttyp4
fd0c ptyp7 rrz0d rrz4b rz21h ttyp5
fddrive ptyp8 rrz0e rrz4c rz29a ttyp6
kbinlog ptyp9 rrz0f rrz4d rz29b ttyp7
kcon ptypa rrz0g rrz4e rz29c ttyp8
keyboard0 ptypb rrz0h rrz4f rz29d ttyp9
klog ptypc rrz16a rrz4g rz29e ttypa
kmem ptypd rrz16b rrz4h rz29f ttypb
lat ptype rrz16c rrz8a rz29g ttypc
lockdev ptypf rrz16d rrz8b rz29h ttypd
log ptyq0 rrz16e rrz8c rz30a ttype
lp0 ptyq1 rrz16f rrz8d rz30b ttypf
mem ptyq2 rrz16g rrz8e rz30c ttyq0
mmsess0 ptyq3 rrz16h rrz8f rz30d ttyq1
mo0 ptyq4 rrz17a rrz8g rz30e ttyq2
mo0.FX729 ptyq5 rrz17b rrz8h rz30f ttyq3
mo0a ptyq6 rrz17c rz0a rz30g ttyq4
mo0a.FX729 ptyq7 rrz17d rz0b rz30h ttyq5
mo0c ptyq8 rrz17e rz0c rz4a ttyq6
mo0c.FX729 ptyq9 rrz17f rz0d rz4b ttyq7
mouse0 ptyqa rrz17g rz0e rz4c ttyq8
msb0 ptyqb rrz17h rz0f rz4d ttyq9
nrmt0a ptyqc rrz21a rz0g rz4e ttyqa
nrmt0h ptyqd rrz21b rz0h rz4f ttyqb
nrmt0l ptyqe rrz21c rz16a rz4g ttyqc
nrmt0m ptyqf rrz21d rz16b rz4h ttyqd
nrmt1a rcdrom rrz21e rz16c rz8a ttyqe
nrmt1h rfd0a rrz21f rz16d rz8b ttyqf
nrmt1l rfd0c rrz21g rz16e rz8c ws0
nrmt1m rmo0 rrz21h rz16f rz8d zero
nrmt1x rmo0.FX729 rrz29a rz16g rz8e
null rmo0a rrz29b rz16h rz8f
pfcntr rmo0a.FX729 rrz29c rz17a rz8g
pipe rmo0c rrz29d rz17b rz8h

Then I try dd if =dev/rz0c of=/mnt/OdysseyFX.img bs=128k, it is ok but im not sure if the device is true.

I have copied the image, it taked 11 hrs !!!!, windows make a restart due to some error during copy, but the "dd" go on copying automatically after the restart.

this is the output:


dd if =dev/rz0c of=/mnt/OdysseyFX.img bs=128k

NFS3 server "windows" not responding still trying (this during the restart)
NFS3 server "windows" ok
16056+1 records in
16056+1 records out


The size of OdysseyFX.img in windows is (1.95 GB, 2,104,565,760 bytes), size on disk is the same, the physical disk is 2GB, with about 10 MB free space in / , and 581 MB free space in /img0.

error:

my PC in single core, celeron 3.4, Ram 875.

how to test it at least before buy new dual core?

From your 'scu' output, RZ28 is 0/0/0, so yes it is /dev/rz0 (or /dev/rrz0).
The dd should be from rz0c, which is what you did.
The resulting size looks reasonable.
So you should be able to boot an emulator from OdysseyFX.img.

However, as you say, you will need to find a system with at least 2xCores, and 2GB of memory (~1G may work, but slowly).

If you can't find one, PM me (or Bruce) and perhaps we could test it for you ?

John M