I have problem when setup Digital Unix 3.2G V62

I have just download FreAXD and i seted up for my system. But i could not do this because i have met problem when started setup.
Please help me to solve this problem.

This my problem:

ff.fe.fd.fc.fb.fa.f9.f8.f7.
ERROR: ISA table corrupt!
Initializing table to defaults
type >>>init to use these changes
f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.
TIMER_TPS environment variable invalid
Defaulting to 1mS per tick
e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>>show device
dka0.0.0.6.0 DKA0 RZ58 2000
dka100.1.0.6.0 DKA100 RZ58 2000
dka400.4.0.6.0 DKA400 RRD42 4.5d
dva0.0.0.0.1 DVA0
ewa0.0.0.11.0 EWA0 08-00-2B-DE-50-00
pka0.7.0.6.0 PKA0 SCSI Bus ID 7
>>>boot dka400
(boot dka400.4.0.6.0 -flags 0)
block 0 of dka400.4.0.6.0 is a valid boot block
reading 16 blocks from dka400.4.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

OSF boot - Mon Jul 24 21:56:39 EDT 1995

Loading hupdate ...
Starting hupdate at 0x20000000
Loading hvmunix ...
Current PAL Revision <0x1000000010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100000002012e>
Loading into KSEG Address Space

Sizes:
text = 4599456
data = 5592320
bss = 1527216
Starting at 0xfffffc00002392e0

B-cache could not be auto-sized
Alpha boot: available memory from 0xf60000 to 0x7ffe000
Digital UNIX V3.2G (Rev. 62); Thu Jul 18 22:31:19 EDT 1996
physical memory = 128.00 megabytes.
available memory = 112.64 megabytes.
using 484 buffers containing 3.78 megabytes of memory
AlphaServer 400 4/166 system
DECchip 21071
82378IB (SIO) PCI/ISA Bridge
Firmware revision: 7.0
PALcode: OSF version 1.46
Module 1011:19 not in pci_option data table, can't configure it
pci0 at nexus
psiop0 at pci0 slot 6
Loading SIOP: script 801a00, reg 82000400, data 40ce3960
scsi0 at psiop0 slot 0
rz0 at scsi0 bus 0 target 0 lun 0 (DEC RZ58 (C) DEC 2000)
rz1 at scsi0 bus 0 target 1 lun 0 (DEC RZ58 (C) DEC 2000)
rz4 at scsi0 bus 0 target 4 lun 0 (DEC RRD42 (C) DEC 4.5d)
isa0 at pci0
gpc0 at isa0
ace0 at isa0
dli: configured



WARNING: preposterous time in TOY -- CHECK AND RESET THE DATE!

vm_swap_init: warning /sbin/swapdefault swap device not found
vm_swap_init: in swap over commitment mode

INIT: SINGLE-USER MODE
/dev/rz4c on /kit: No valid filesystem exists on this partition
Cannot mount CDROM rz4c on /kit.
# init 3

INIT: New run level: 3

INIT: New run level: S

INIT: SINGLE-USER MODE
/dev/rz4c on /kit: No valid filesystem exists on this partition
Cannot mount CDROM rz4c on /kit.
# mount /dev/rz4c /kit
/dev/rz4c on /kit: Read-only file system
# init 3

INIT: New run level: 3

INIT: New run level: S
INIT: SINGLE-USER MODE
/dev/rz4c on /kit: No valid filesystem exists on this partition
Cannot mount CDROM rz4c on /kit.

Best regards.

Lhnhan

Thanks for being the 1st person to report results for 3.2G !

The log indicates that there is a problem reading/understanding the format of the CD (rz4). This is possibly a function of the version of FreeAXP that you are running. What version did you test with, and on what Windows platform ?

FreeAXP boots fine from CD for V3.2C and V4.0D, so we would expect V3.2G to work as well, but, alas, we've not been able to test V3.2G yet since we've been unable to locate a V3.2G kit to test with.

Also, as with V3.2C through V4.0D, you will need to set pka0_disconnect to 0. The release notes at their next revision will state :

"[i:]Tru64 UNIX versions from V3.2x up to and including V4.0D require the setting of pka0_disconnect to 0. On systems with dual SCSI HBAs there will be a pka0 and a pkb0 (Avanti and Avanti Flex), ensure both have disconnect set to 0.

eg.

>>> show pka*
pka0_disconnect 1
....
>>> set pka0_disconnect 0
>>> init[/i:]"

Try the pka0 setting, and see if that helps the CD.

Also, if the physical CD doesn't co-operate, booting from an image copy of the V3.2G CD -may- work better.

regards,
John M

< class='quote'>[b:]John Manger wrote:[/b:]
Lhnhan

Thanks for being the 1st person to report results for 3.2G !

The log indicates that there is a problem reading/understanding the format of the CD (rz4). This is possibly a function of the version of FreeAXP that you are running. What version did you test with, and on what Windows platform ?

FreeAXP boots fine from CD for V3.2C and V4.0D, so we would expect V3.2G to work as well, but, alas, we've not been able to test V3.2G yet since we've been unable to locate a V3.2G kit to test with.

Also, as with V3.2C through V4.0D, you will need to set pka0_disconnect to 0. The release notes at their next revision will state :

"[i:]Tru64 UNIX versions from V3.2x up to and including V4.0D require the setting of pka0_disconnect to 0. On systems with dual SCSI HBAs there will be a pka0 and a pkb0 (Avanti and Avanti Flex), ensure both have disconnect set to 0.

eg.

&gt;&gt;&gt; show pka*
pka0_disconnect 1
....
&gt;&gt;&gt; set pka0_disconnect 0
&gt;&gt;&gt; init[/i:]"

Try the pka0 setting, and see if that helps the CD.

Also, if the physical CD doesn't co-operate, booting from an image copy of the V3.2G CD -may- work better.

regards,
John M
Hello Jonh
Thanks for your anwser my question.
My CD boot was format UFS file system.
I give you this CD image and please help me to chech problem.
megashare.vn/dl.php/2771775
megashare.vn/dl.php/2771807
megashare.vn/dl.php/2771838
megashare.vn/dl.php/2771874
megashare.vn/dl.php/2772138

Thanks a lot.

Please check your PM inbox.

John M