Question Seagate Ontrack Dynamic Drive Overlay Virtualbox

suvadhodzic · Nov 12, 2020

Can anybody help about this issue:

We have some old machine and cloned the drive (1Gig CF cloned RAW image).
We are having troubles with virtualization of OS2 Warp3 OS.
Since old bios of machine does not support bigger disks on disk is installed Seagate ONTRACK Dynamic Disk Overlay.

We are trying to virtualize the PC on it by cloning raw image and convertiong it to virtual disk and then run it in VM (mostly this works, but Seagate ontrack fails in this case)

Here is a picture

Made vdi from with convertfromraw it but when we try to boot up Seagate Tool is failing..
The machine has old bios
VDI Geometry is exactly as in original bios.
Does anyone knows how to fix seagate DDO problem and not to ruin data on the disk?
Any help is appreciated. Thank you in advance.

fzabkar · Nov 12, 2020

Can you carve out and upload the first track (17 sectors?) with a hex editor? ISTR that the code in sector 0 (the dummy MBR) calls and loads INT13 extensions in subsequent sectors, and then transfers control to the real, full capacity MBR somewhere in track 0.

Alternatively, there may be a HPA (Host Protected Area) which is uncovered after bootup for the duration of the current power cycle.

https://forums.tomshardware.com/thr...ig-available-after-removal-of-ontrack.654882/

suvadhodzic · Nov 13, 2020

fzabkar said:
Can you carve out and upload the first track (17 sectors?) with a hex editor? ISTR that the code in sector 0 (the dummy MBR) calls and loads INT13 extensions in subsequent sectors, and then transfers control to the real, full capacity MBR somewhere in track 0.

Alternatively, there may be a HPA (Host Protected Area) which is uncovered after bootup for the duration of the current power cycle.

https://forums.tomshardware.com/thr...ig-available-after-removal-of-ontrack.654882/

Here it is:
1. RAW IMAGE:
https://ibb.co/R3qT1gN

raw2 hosted at ImgBB

Image raw2 hosted in ImgBB

ibb.co

https://ibb.co/1fBzxMR

2. Converted VDI
https://ibb.co/F0rVFjx

vdi2 hosted at ImgBB

Image vdi2 hosted in ImgBB

ibb.co

fzabkar · Nov 13, 2020

It would be easier for us if you could upload the binary data rather than a picture of the data.

In any case I can see a real partition table in sector 0. The partition ID is 54h, which is an OnTrack Disk Manager 6 Dynamic Drive Overlay (DDO).

https://en.wikipedia.org/wiki/Partition_type

The partition begins at LBA 9 and has a size of 1956519 sectors.

Code:

Disk identifier (Windows):
00000000h
Boot  System ID   :   First    :    Last    : Relative : Number of:
Flag              :Cyl Head Sec:Cyl Head Sec:  Sector  :  Sectors :
80h 54h ??        :   0   0 10 :1023  15 63 :         9:   1956519:  1.00 GB
00h 00h           :   0   0  0 :   0   0  0 :         0:         0:        0
00h 00h           :   0   0  0 :   0   0  0 :         0:         0:        0
00h 00h           :   0   0  0 :   0   0  0 :         0:         0:        0
MBR signature (0xAA55):

This would suggest that the boot sector for the partition would be at LBA 9, ie offset 0x1200. However, your dump shows a "RESERVED" block at this point???

My approach would be to remove the DDO. To this end I would locate the boot sector and then edit the partition table to point to it. I would also replace Ontrack's MBR boot code with standard MS-DOS or OSX boot code.

https://thestarman.pcministry.com/asm/mbr/STDMBR.htm

You could do all this with a free disc editor, DMDE. I could help you if needed. DMDE can also mount the image and view the files.

Could you show us the Partitions window in DMDE?

https://dmde.com/

suvadhodzic · Nov 14, 2020

Sorry for the images.
Here is raw disk image
https://www.transfernow.net/Ofnkcl112020
How to remove DDO with DMDE? I can remove DDO with Seagate Tools when I boot VDI.

Do not understand "To this end I would locate the boot sector and then edit the partition table to point to it. I would also replace Ontrack's MBR boot code with standard MS-DOS or OSX boot code. " (never edited this before)

suvadhodzic · Nov 14, 2020

These are the real partitions (OS2) partitions.

https://ibb.co/8mvDJY5

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

https://ibb.co/tLZqbGX

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

https://ibb.co/6rYgCg6

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

https://ibb.co/VVc8jst

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

suvadhodzic · Nov 14, 2020

Here is original BIOS user from CNC machine PC:

https://ibb.co/cy8zwYN

fzabkar · Nov 14, 2020

Your image has a HPFS boot sector at sector 126. There is a partition table at sector 63.

ISTM that all you need to do is to remove the first 63 sectors (0x7E00 bytes) from your image file. You can do this with your hex editor. (I use HxD, freeware.)

Code:

 LBA:63                 block: 63
Disk identifier (Windows):
00000000h
Boot  System ID   :   First    :    Last    : Relative : Number of:
Flag              :Cyl Head Sec:Cyl Head Sec:  Sector  :  Sectors :
80h 07h NTFS/exFAT:   0   1  1 : 507  31 63 :        63:   1024065:   524 MB
00h 00h           :   0   0  0 :   0   0  0 :         0:         0:        0
00h 00h           :   0   0  0 :   0   0  0 :         0:         0:        0
00h 00h           :   0   0  0 :   0   0  0 :         0:         0:        0
MBR signature (0xAA55):
AA55h

Code:

OS/2 MBR code at LBA 63

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00007E00  90 E9 79 01 FA 33 C0 8E D0 8E C0 8E D8 BC 00 7C  .éy.ú3ÀŽÐŽÀŽØ¼.|
00007E10  8B F4 FB BF 00 06 B9 00 01 F3 A5 BB 20 06 FF E3  ‹ôû¿..¹..ó¥» .ÿã
00007E20  90 90 BE 79 07 81 3C AA 55 75 11 E8 58 00 73 0C  ..¾y..<ªUu.èX.s.
00007E30  E8 61 00 72 07 E8 AD 00 72 3B EB 2C BE 79 07 C7  èa.r.è..r;ë,¾y.Ç
00007E40  04 00 00 BA 80 00 BE BE 07 B9 04 00 F6 04 80 75  ...º€.¾¾.¹..ö.€u
00007E50  07 83 C6 10 E2 F6 EB 1D 8A 74 01 8B 4C 02 BB 00  .ƒÆ.âöë.Št.‹L.».
00007E60  7C B8 01 02 CD 13 72 0D 81 3E FE 7D 55 AA 75 05  |¸..Í.r..>þ}Uªu.
00007E70  EA 00 7C 00 00 BE 66 07 AC 0A C0 74 FE BB 07 00  ê.|..¾f.¬.Àtþ»..
00007E80  B4 0E CD 10 EB F2 BB 00 7E C6 07 0A B2 80 B8 00  ´.Í.ëò».~Æ..²€¸.
00007E90  E0 CD 13 C3 BF 00 7E BA F0 01 B3 A0 E8 84 00 72  àÍ.Ã¿.~ºð.³ è„.r
00007EA0  0C B1 01 E8 48 00 72 05 E8 19 00 73 16 F6 C3 10  .±.èH.r.è..s.öÃ.
00007EB0  75 05 80 CB 10 EB E5 81 FA 70 01 74 05 BA 70 01  u.€Ë.ëå.úp.t.ºp.
00007EC0  EB D8 F9 C3 81 BD FE 01 55 AA 75 17 8B 75 02 81  ëØùÃ.½þ.Uªu.‹u..
00007ED0  FE BE 01 77 0E 03 F7 81 3C AA 55 75 06 F6 44 02  þ¾.w..÷.<ªUu.öD.
00007EE0  01 75 01 F9 C3 BF 00 7C B1 0A E8 01 00 C3 52 57  .u.ùÃ¿.|±.è..ÃRW
00007EF0  83 C2 02 B0 01 EE 42 8A C1 EE 42 32 C0 EE 42 EE  ƒÂ.°.îBŠÁîB2ÀîBî
00007F00  42 8A C3 EE 42 B0 20 EE E8 33 00 EC 24 FD 3C 58  BŠÃîB° îè3.ì$ý<X
00007F10  75 0D 83 EA 07 B9 00 01 FA F3 6D FB F8 EB 01 F9  u.ƒê.¹..úómûøë.ù
00007F20  5F 5A C3 52 83 C2 07 EC A8 80 75 0F 4A 8A C3 EE  _ZÃRƒÂ.ì¨€u.JŠÃî
00007F30  42 EC 24 D0 3C 50 75 03 F8 EB 01 F9 5A C3 51 8B  Bì$Ð<Pu.øë.ùZÃQ‹
00007F40  0E 6C 04 83 C1 12 81 C2 FF 01 EC 8A E0 80 E4 D8  .l.ƒÁ..Âÿ.ìŠà€äØ
00007F50  80 FC 58 74 06 3B 0E 6C 04 75 EF 81 EA FF 01 B9  €üXt.;.l.uï.êÿ.¹
00007F60  00 20 E2 FE 59 C3 0D 0A 45 72 72 6F 72 20 4C 6F  . âþYÃ..Error Lo
00007F70  61 64 69 6E 67 20 4F 53 00 55 AA 00 00 E9 84 FE  ading OS.Uª..é„þ
00007F80  00 00 00 00 6C 00 00 00 00 00 00 00 00 00 00 00  ....l...........
00007F90  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00007FA0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00007FB0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01  ..............€.
00007FC0  01 00 07 1F 7F FB 3F 00 00 00 41 A0 0F 00 00 00  .....û?...A ....
00007FD0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00007FE0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00007FF0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  ..............Uª

Code:

 LBA:126                block: 126
OEM identifier         "OS2 20.0"
Bytes per Sector        512
Sectors per Cluster     16
Reserved Sectors        1
Number of FATs          0
Root Dir Entries        512
Total Sectors           0
Media Descriptor        F8h
Sectors per FAT         250
Sectors per Track       63
Number of Heads         32
Hidden Sectors          63
Total Sectors           1024065
Not Used (0x00800080)   15280080h
Total NTFS Sectors      55333400170992
MFT Start Cluster       5784873721357402112
MFT Mirror Cluster      35322350031686
Clusters per FILE       0                   (0 bytes)
Clusters per INDX       0                   (0 bytes)
Serial Number (hex)     00000000-FA000000h
Checksum                D08EC033h
Boot Signature (0xAA55) AA55h

Code:

 LBA:126                block: 126
0000fc00: EB 4D 90 4F 53 32 20 32  30 2E 30 00 02 10 01 00  ëMOS2 20.0.....
0000fc10: 00 00 02 00 00 F8 FA 00  3F 00 20 00 3F 00 00 00  .....øú.?. .?...
0000fc20: 41 A0 0F 00 80 00 28 15  F0 51 A9 4F 53 32 00 00  A ..€.(.ðQ©OS2..
0000fc30: 00 00 00 00 00 00 48 50  46 53 20 20 20 20 00 00  ......HPFS    ..
0000fc40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 FA  ...............ú
0000fc50: 33 C0 8E D0 BC 00 7C FB  B8 C0 07 8E D8 A1 24 00  3ÀŽÐ¼.|û¸À.ŽØ¡$.
0000fc60: A3 4D 00 CD 12 2D 4C 00  25 F0 FF C1 E0 06 A3 4B  £M.Í.-L.%ðÿÁà.£K
0000fc70: 00 C7 06 3E 00 00 00 C7  06 40 00 00 00 C7 06 45  .Ç.>...Ç.@...Ç.E
0000fc80: 00 14 00 A1 4B 00 8E C0  2B DB E8 21 00 FF 36 4B  ...¡K.ŽÀ+Ûè!.ÿ6K
0000fc90: 00 68 72 02 A1 4D 00 26  A3 4D 00 26 A2 24 00 A1  .hr.¡M.&£M.&¢$.¡
0000fca0: 1C 00 26 A3 1C 00 A1 1E  00 26 A3 1E 00 CB 50 53  ..&£..¡..&£..ËPS
0000fcb0: 51 52 06 A1 3E 00 8B 16  40 00 03 06 1C 00 13 16  QR.¡>.‹.@.......
0000fcc0: 1E 00 50 A1 1A 00 F6 26  18 00 8B C8 58 F7 F1 A3  ..P¡..ö&..‹ÈX÷ñ£
0000fcd0: 42 00 8B C2 F6 36 18 00  FE C4 88 26 44 00 A2 25  B.‹Âö6..þÄˆ&D.¢%
0000fce0: 00 A1 18 00 2A 06 44 00  40 3B 06 45 00 76 03 A1  .¡..*.D.@;.E.v.¡
0000fcf0: 45 00 50 B4 02 8B 16 42  00 B1 06 D2 E6 0A 36 44  E.P´.‹.B.±.Òæ.6D
0000fd00: 00 8B CA 86 E9 8B 16 24  00 CD 13 58 72 2A 01 06  .‹Ê†é‹.$.Í.Xr*..
0000fd10: 3E 00 83 16 40 00 00 29  06 45 00 76 0B C1 E0 05  >.ƒ.@..).E.v.Áà.
0000fd20: 8C C2 03 D0 8E C2 EB 8B  07 5A 59 5B 58 C3 BE 6E  ŒÂ.ÐŽÂë‹.ZY[XÃ¾n
0000fd30: 08 EB 08 BE 02 02 EB 03  BE 58 01 E8 09 00 BE 3E  .ë.¾..ë.¾X.è..¾>
0000fd40: 02 E8 03 00 FB EB FE AC  3C 00 74 09 B4 0E BB 07  .è..ûëþ¬<.t.´.».
0000fd50: 00 CD 10 EB F2 C3 1D 00  41 20 64 69 73 6B 20 72  .Í.ëòÃ..A disk r
0000fd60: 65 61 64 20 65 72 72 6F  72 20 6F 63 63 75 72 72  ead error occurr
0000fd70: 65 64 2E 0D 0A 00 07 4F  53 32 4B 52 4E 4C 06 4F  ed.....OS2KRNL.O
0000fd80: 53 32 4C 44 52 07 4F 53  32 42 4F 4F 54 00 00 00  S2LDR.OS2BOOT...
0000fd90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0000fda0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0000fdb0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0000fdc0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0000fdd0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0000fde0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
0000fdf0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 AA  ..............Uª

Those additional Volumes that DMDE has found are probably boot sector templates stored within OS files such as FORMAT.COM, FDISK.EXE, etc.

It appears that DMDE doesn't understand HPFS. I have no experience with HPFS, either.

suvadhodzic · Nov 14, 2020

Thank you. That did the trick.
Now I got rid of DDO and OS2 is trying to boot but fails 🙁.
This now is not DDO or disk problem.

Virtual box is not reporting any problems in logs but i it is stuck on blank screen:

"
00:00:06.238544 VMEmt: Halt method global1 (5)
00:00:06.238653 VMEmt: HaltedGlobal1 config: cNsSpinBlockThresholdCfg=50000
00:00:06.238668 Changing the VM state from 'CREATING' to 'CREATED'
00:00:06.240078 Changing the VM state from 'CREATED' to 'POWERING_ON'
00:00:06.240154 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:06.240177 Console: Machine state changed to 'Running'
00:00:06.245268 VMMDev: Guest Log: BIOS: VirtualBox 6.1.16
00:00:06.245447 PCI: Setting up resources and interrupts
00:00:06.247163 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:06.274944 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:06.276320 VMMDev: Guest Log: CPUID EDX: 0x178bfbff
00:00:06.276449 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:06.276501 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:06.277219 VMMDev: Guest Log: BIOS: ata0-0: PCHS=1941/16/63 LCHS=970/32/63
00:00:06.279961 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:06.296503 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000c2f0000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
00:00:06.741271 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:06.752911 GUI: 2D video acceleration is disabled
00:00:06.753357 GUI: HID LEDs sync is enabled
00:00:06.784861 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:08.793619 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:08.802838 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:08.803382 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0021
00:00:08.867543 VMMDev: Guest Log: BIOS: Boot from Floppy 0 failed
00:00:08.868682 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0002
00:00:08.870196 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:08.880177 VMMDev: Guest Log: BIOS: *** int 15h function AX=0400, BX=e6f5 not yet supported!
00:00:08.884446 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:08.889981 VMMDev: Guest Log: int13_harddisk: function 15, unmapped device for ELDL=81
00:00:08.960192 RTC: period=0x400 (1024) 32 Hz
00:00:10.589877 GUI: UIFrameBufferPrivate:😛erformResize: Size=720x400, Using fallback buffer since no source bitmap is provided
00:00:10.757299 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000c2f0000 w=640 h=480 bpp=0 cbLine=0x140 flags=0x0 origin=0,0
00:00:11.123663 RTC: period=0x100 (256) 128 Hz
00:00:14.383077 ATA: LUN#0: INITIALIZE DEVICE PARAMETERS: 63 logical sectors, 15 heads
00:00:21.053592 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=640 h=480 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:21.053898 GUI: UIFrameBufferPrivate:😛erformResize: Size=640x480, Using fallback buffer since no source bitmap is provided
00:00:21.099835 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:21.229731 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:22.868753 GUI: UIFrameBufferPrivate:😛erformResize: Size=720x400, Using fallback buffer since no source bitmap is provided"

So I'm stuck here. Probably some internal OS2 problem with some HW initialization..

https://ibb.co/XFRGjJv

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

https://ibb.co/fGr9cDL

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

If you got any advices would be greatfull..

Thanks a lot if not you helped with DDO alot..

suvadhodzic · Nov 14, 2020

... or maybe still. ..

00:00:08.889981 VMMDev: Guest Log: int13_harddisk: function 15, unmapped device for ELDL=81

fzabkar · Nov 14, 2020

IIUC, the code is calling a BIOS function (INT 15h, function 400h) which does not exist in VirtualBox. It could be a vendor specific interrupt.

00:00:08.880177 VMMDev: Guest Log: BIOS: *** int 15h function AX=0400, BX=e6f5 not yet supported!

https://www.stanislavs.org/helppc/int_15.html
https://oldlinux.superglobalmegacorp.com/Linux.old/docs/interrupts/int-html/int-15.htm

This function (INT 13h, function 15h) is trying to identify the storage device:

00:00:08.889981 VMMDev: Guest Log: int13_harddisk: function 15, unmapped device for ELDL=81

https://www.stanislavs.org/helppc/int_13.html
https://oldlinux.superglobalmegacorp.com/Linux.old/docs/interrupts/int-html/int-13.htm

INT 13,15 Read disk type/DASD type (XT BIOS from 1/10/86 & newer)

The corresponding assembly language codes are CD 15 and CD 13.

Edit:

I found this thread:

[Solved] int13_harddisk: function 15, unmapped device for ELDL=82:
https://forums.virtualbox.org/viewtopic.php?t=91365

Maybe you have come to the wrong forum?

fzabkar · Nov 14, 2020

I wonder if Virtualbox can make use of a BIOS dump. That would give it access to unsupported BIOS interrupts.

BTW, you can dump your BIOS using MSDOS debug.exe, if you can boot from a floppy diskette. I could help you with that, if needed.

fzabkar · Nov 15, 2020

I wonder if it would be worth playing with a working OS/2 Ver 3 VM.

OS/2 on Virtualbox Guide:
https://gekk.info/articles/os2.html

Prebuilt VM images:
https://gekk.info/os2_ovas/
https://gekk.info/os2_ovas/os2_warp_3.ova
https://gekk.info/os2_ovas/os2_warp_3_snap.ova

BTW, I compressed your 1GB image down to 50MB. If you like, and if the data are not private, I can host it on my own web space.

suvadhodzic · Nov 15, 2020

I managed to boot it up.. had to use "MAKEINI" from "OS2" and it booted as it should.
Now have other problems with software inside (graphics not ok).. but OS2 is up and running..
So thank you.. Can mark as solved

Ty a lot..

fzabkar · Nov 15, 2020

Yours looks like an interesting job. I had some fun with another CNC machine in another forum.

BTW, your 1GB image can be reduced by half to correspond to the actual size of the HPFS volume, ie 524MB. That corresponds to the range 0x7E00 to 0x14F17E00. The "F6" pattern is written by the OS/2 formatter.

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

1F417DD0  F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6
1F417DE0  F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6
1F417DF0  F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6
1F417E00  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
1F417E10  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
1F417E20  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

suvadhodzic · Nov 15, 2020

fzabkar said:
Yours looks like an interesting job. I had some fun with another CNC machine in another forum.

BTW, your 1GB image can be reduced by half to correspond to the actual size of the HPFS volume, ie 524MB. That corresponds to the range 0x7E00 to 0x14F17E00. The "F6" pattern is written by the OS/2 formatter.

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 1F417DD0 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 1F417DE0 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 1F417DF0 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 F6 1F417E00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 1F417E10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 1F417E20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Not a big problem. Bigger one it has CAD sw and I cannot run it because graphics driver... so.. i give up because Oracle said: "Why should VirtualBox support Win95 when Microsoft does not". (same is for OS2Warp3 graphics)
So.. Maybe if I catch more time I'll try to setup guest additions and try to fix the graphics problem.

fzabkar · Nov 15, 2020

Would you permit me to host a compressed image of your drive on my web space so that I can ask data recovery people in other forums to extract the files from the HPFS volume (assuming the contents are not private or proprietary)?

BTW, I'm assuming that your machine was made by IMA:

https://wtp.hoechsmann.com/lexikon/6623/IMA

.. and that you are running IMAWOP 2.6 software:

https://wtp.hoechsmann.com/en/lexikon/6764/imawop

suvadhodzic · Nov 15, 2020

fzabkar said:
Would you permit me to host a compressed image of your drive on my web space so that I can ask data recovery people in other forums to extract the files from the HPFS volume (assuming the contents are not private or proprietary)?

BTW, I'm assuming that your machine was made by IMA:

https://wtp.hoechsmann.com/lexikon/6623/IMA

.. and that you are running IMAWOP 2.6 software:

https://wtp.hoechsmann.com/en/lexikon/6764/imawop

Yes we run IMAWOP 2.6 (you can host it).
I cannot run it (don't know the reason) probably graphics issue or it is trying to access some controller or somethig from CNC.
I converted rawimage with VBoxManage and entered console and used MAKEINI to fix boot problem. Now I am stuck runnig IMAWOP.

fzabkar · Nov 15, 2020

How is the PC connected to the CNC machine? Is there a proprietary interface card?

This is your HPFS volume (compressed to 48 MiB):

http://www.users.on.net/~fzabkar/HDD/CNCNovaFrontaCFImage_HPFS_volume.7z

suvadhodzic · Nov 16, 2020

fzabkar said:
How is the PC connected to the CNC machine? Is there a proprietary interface card?

This is your HPFS volume (compressed to 48 MiB):

http://www.users.on.net/~fzabkar/HDD/CNCNovaFrontaCFImage_HPFS_volume.7z

Sincearly do not know. But I think there is, because there is a special PC and Machine SW it self is on this image..

fzabkar · Nov 16, 2020

I just found out that all the professional data recovery tools are unable to recognise HPFS volumes. I was expecting that it would be easy to extract the files from the disk image, but not so. I'll have to break out my floppy drive and boot up OS/2.

The only CNC machine I remember being involved with (a Japanese brand) had an RS232 port, but that was 35 years ago.

suvadhodzic · Nov 16, 2020

fzabkar said:
I just found out that all the professional data recovery tools are unable to recognise HPFS volumes. I was expecting that it would be easy to extract the files from the disk image, but not so. I'll have to break out my floppy drive and boot up OS/2.

The only CNC machine I remember being involved with (a Japanese brand) had an RS232 port, but that was 35 years ago.

Basically you do not have to.

You can use VirtualBox.

VBoxManage convertfromraw rawimageisenttoyou OutputFile.vdi

Use this vdi to boot up virtual machine.

Before OS2 Logo press ALT+F1 or CRTL+ALT+F1 then on recovery windows choose "C" to get to console..
Then recreate ini files to get your desktop back:
Like.

CD OS2<Enter>
MAKEINI OS2.INI INI.RC <Enter>
MAKEINI OS2SYS.INI INISYS.RC <Enter>

Reboot and you will boot OS2 desktop with IMA and whole OS2.
To kill cnc sw use Alt-Esc and then Delete key to kill it.
then you will have control over IMA sw and OS2.

fzabkar · Nov 16, 2020

I'm using 32-bit Win 10, so I had to use VirtualBox version 5.2.44 r139111 (Qt5.6.2). Unfortunately it doesn't like the VB image.

Code:

Failed to open virtual machine located in C:/FZWork/temp/Ontrack_DDO/CNCNovaFrontaCFImage_HPFS_volume.vbox.

Extra content at the end of the document.

Location: 'C:\FZWork\temp\Ontrack_DDO\CNCNovaFrontaCFImage_HPFS_volume.vbox', line 1 (0), column 2.

F:\tinderbox\win-5.2\src\VBox\Main\src-server\MachineImpl.cpp[483] (long __thiscall Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &amp;,const class com::Guid *)).

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}

However, I was able to use DFSee to open the Vbox image and recover the files to another drive.

https://www.dfsee.com/

There was one file that caused DFSee to hang consistently, namely \IBMCOM\prn.msg. I don't know the reason for this.

Here are the files:

http://www.users.on.net/~fzabkar/HDD/CNC_OS2_Files.7z

suvadhodzic · Nov 17, 2020

Don't bother. I will upload you working .vdi so you can use that with latest VirtualBox.

fzabkar · Nov 17, 2020

I think you only need to upload the Vbox header (0 - 0x20000). In any case I can't run 64-bit versions of VBox on my 32-bit OS, so it would be pointless. Moreover, since DFSee can parse my VBox image, then it must be OK.

Question Seagate Ontrack Dynamic Drive Overlay Virtualbox

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Illustrious

Share this page