Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Ontrack Disk Manager 10.46 Iso Download
439 views
Skip to first unread message
Beatzby Wall
Jan 2, 2024, 10:05:33 AM1/2/24
to
For reference I used the same CF Card with both packages (a 16 GB Sandisk Ultra card) and the CF adapter is a Delock 91655.
If it makes any difference I copied the contents of those 2 packages to some win98 boot floppy images and booted them using CD's and over the network using PXE with the same result.
ontrack disk manager 10.46 iso download
Download File https://t.co/6Csge23hGJ
Unfortunately - due to the nature of IMDISK being a volume (and not a disk) virtual driver - it hooks not to many of the usual windows subsystems, so mountvol, diskpart and disk manager cannot be used to see what is happening and you need a hex view of the first sector to check it is actually the bootsector/PBR.
If from the IMDISK GUI you have available the mounted drive and press the "Save Image" button, you should have the option to save the image "as is" (aka volume or "superfloppy") or to prepend to it a MBR (without booting code but with valid partition table) and 62 empty sectors[1], in practice a valid "whole disk" image that you can dd to another media, essentially stripping the Ontrack overlay.
Ontrack Disk Manager mangles disk partitions in a way that prevents Linux from seeing where a partition starts. So there is no easy way to mount a FAT32 partition on a OTDM disk. I searched for a way for mounting these partitions on Linux but found nothing on the internet. I discovered this method myself so I thought I should document it here.
- Ontrack Disk Manager 9.57 from Phil's Computer Lab: -disk-manager.html
- Install Ontrack Disk Manager on the retro computer and create and format a single big partition as FAT32 and install os on it.
- Move the disk to a Linux computer and search for the start of the FAT32 partition by opening the disk (in this example: /dev/sde1) to a hex editor:
2) Don't know exactly about ontrack, but EzDrive has a small sys file you can load to free up all the conventional memory it otherwise consumes. (OnTrack consumes 10kB, EzDrive consumes 5kB - with loading that sys file, it's 0kB for EzDrive)
1. Generally you should avoid v10.x, specially in older machines were DDO would be required. v10.x comes as a PartitionMagic-like GUI dos app, but it is pretty limited, and almost useless in older machines were you would like to use stuff like "true" low level format and mfm/rll disk configuration. Stick with v9.57
2. OntrackW.386 is only required for win3x and win95 rtm (floppy based install) if you want to use 32bit disk access. Check it would or wouldn't work with external controllers which have their own BIOS, as some IDE and almost all SCSI cards.
3. You can try disabling Ontrack protection-aware partition table format when preparing your disk to use DDO. Ontrack floppies come with an online manual which tells you the switches you have to pass the app in order to enable or disable certain features, like disabling ontrack format or relocating DDO when a memory manager is available.
I'm playing around with Ontrack Disk Manager 9.57 to get a 32G CF card working with my 386 build. I have DOS 6.22 so I had it configured 4 partitions of 2G each. It's working great except that I notice it reduces DOS memory by around 15k. Is this typical? Also the manual says it can relocate much of itself to UMBs with the /L=2 parameter. Has anyone ever tried this with success? It doesn't seem to do anything with my build. I do have EMM386 loaded and can load mouse or cd-rom drivers into UMBs with no issue. This is not about loading the ONTRACKD.SYS driver, but the disk overlay itself, which is loaded by MBR and before DOS I assume. Technically I would be very impressed if this is actually feasible at all. ?
I didn't realize the SIIG EIDE card I have around actually supports disks up to 8.4G. I tried it yesterday and it works great except for some reason the BIOS on this card reserve 2k from DOS. So I end up with 638K for now.
Ontrack needs to modify the MBR and write some of its data to the drive so it can get loaded to memory at boot time, that's why you're supposed to format the drive AFTER Ontrack is active and is doing the translation to access the full capacity of the disk.
ok but how do i know if it worked? its supposedly supposed to take a while to format but it formats in only a few seconds and claims to be done. it also doesn't ask for a boot disk or anything just says to restart.
as of right now with the ontrack drive empty with no windows instalation , the computer doesn't do anything at all with the drive. theres no ontrack word or logo that pops up before it tries to search for an os install
I'm not getting something here,
If the drive is recognized, working fine at full capacity and has a windows installation, then you don't need the overlay software
If the drive is wiped by installing ontrack, why don't you install windows the same way you initially installed it? How did this hard disk end up with windows on it? And no, a windows installation won't erase ontrack.
The only probable scenario I can think of is that the hdd had already windows installed while in another pc and now you want to put it on a pc for which it is too large and needs ontrack. Well in this case you'll need to reinstall everything, somehow.
The only probable scenario I can think of is that the hdd had already windows installed while in another pc and now you want to put it on a pc for which it is too large and needs ontrack. Well in this case you'll need to reinstall everything, somehow.
Ok man I guess I can help you. I have used these kind of disk utilities in the past, but I always just install windows 98 with a OEM 98se cd rom boot disk. Thats what you need.
The kind of Ontrack thing I used was a ontrack kill disk utility that was a drive wiper and it was like kill disk, the other things I used before are partition magic. I have used those ontrack drive overlays.
No matter, I used those programs for specific case rare cases, I alwasy just cam back to a 98se oem cd rom boot disk. Google it if you dont have one.
i dont know what the specs of the drive are its an 8gb dom. And ontrack doesn't seem to specify needing to set any parameters. it's being done on a machine that can already detect the dom anyway then moved to a 486
I could be completely wrong about this, but you might need to install the overlay software on the system where you intend to use it . I am not sure if it will install properly on a system whose BIOS already supports "large" disks . I would also mention that I am not sure any system will actually be able to read or write to the disk with the overlay installed, unless you either boot with from the drive where the overlay is installed or a boot floppy that has a copy of the overlay software .
It's been a long time but I have a vague memory of having to let the PC boot initially from the HDD (with ontrack installed) and then pressing/holding keys down if you need to boot a floppy, to ensure the DDO gets loaded.
But basically
Yes, set this up on the PC you intend to use it on
No, Installing windows wont undo ontracks work as long as you use its spacebar method to boot from floppy (you can see this at 6:57 in the video)
--
NetZ Computing Ltd. ISRAEL sup... resq.co.il
InVircible Anti-Virus Software, ResQdisk and Data Recovery Utilities
E-mail sent in reply to this post will not be considered private and
may be answered in the newsgroup.
It depends. If it's Disk Manager, then removing the dynamic drive overlay (DDO)
without losing the data already on the drive is not a simple task but can be
done. You'll need a disk sector editor for the purpose, good understanding of
disk structures, and guidance. The DM removal tool provided by disk producers
will also remove all your data and files from the drive, not only the boot
overlay. If what you installed is rather EZ-drive and not DM, then the removal is fairly
simple (retaining your data and files in functional state), with either a
Seagate dedicated tool, or with RESQDISK /REBUILD (www.resq.co.il/resq.php).
Read the primer on my page before attempting anything.Regards, Zvi
Thanks for the pointers... I will have to bring home some DOS sector
editor programs and have a look at the boot record (Win ME doesn't have the
"boot to DOS" option). As for which it is... The install was "Disk Wizard" by Seagate, and this
appears to be part of how they regain control after a reboot (part of the
disk data transer procedure). However, the UNINSTALL for Disk Wizard
doesn't touch it (although it did remove anything from the startup
folders). Nothing in the Autoexec or Config files either.The block lettering says "Starting ONTRACK... Disk Wizard".Wouldn't particularly matter except:
a) I don't like things in my system that I didn't intentionally put there.
b) It slows down booting (waits a while with an option to boot from
floppy).
c) It... well, it's the principle of the thing, dang it!!! tnx, jmk
35fe9a5643
If it makes any difference I copied the contents of those 2 packages to some win98 boot floppy images and booted them using CD's and over the network using PXE with the same result.
ontrack disk manager 10.46 iso download
Download File https://t.co/6Csge23hGJ
Unfortunately - due to the nature of IMDISK being a volume (and not a disk) virtual driver - it hooks not to many of the usual windows subsystems, so mountvol, diskpart and disk manager cannot be used to see what is happening and you need a hex view of the first sector to check it is actually the bootsector/PBR.
If from the IMDISK GUI you have available the mounted drive and press the "Save Image" button, you should have the option to save the image "as is" (aka volume or "superfloppy") or to prepend to it a MBR (without booting code but with valid partition table) and 62 empty sectors[1], in practice a valid "whole disk" image that you can dd to another media, essentially stripping the Ontrack overlay.
Ontrack Disk Manager mangles disk partitions in a way that prevents Linux from seeing where a partition starts. So there is no easy way to mount a FAT32 partition on a OTDM disk. I searched for a way for mounting these partitions on Linux but found nothing on the internet. I discovered this method myself so I thought I should document it here.
- Ontrack Disk Manager 9.57 from Phil's Computer Lab: -disk-manager.html
- Install Ontrack Disk Manager on the retro computer and create and format a single big partition as FAT32 and install os on it.
- Move the disk to a Linux computer and search for the start of the FAT32 partition by opening the disk (in this example: /dev/sde1) to a hex editor:
2) Don't know exactly about ontrack, but EzDrive has a small sys file you can load to free up all the conventional memory it otherwise consumes. (OnTrack consumes 10kB, EzDrive consumes 5kB - with loading that sys file, it's 0kB for EzDrive)
1. Generally you should avoid v10.x, specially in older machines were DDO would be required. v10.x comes as a PartitionMagic-like GUI dos app, but it is pretty limited, and almost useless in older machines were you would like to use stuff like "true" low level format and mfm/rll disk configuration. Stick with v9.57
2. OntrackW.386 is only required for win3x and win95 rtm (floppy based install) if you want to use 32bit disk access. Check it would or wouldn't work with external controllers which have their own BIOS, as some IDE and almost all SCSI cards.
3. You can try disabling Ontrack protection-aware partition table format when preparing your disk to use DDO. Ontrack floppies come with an online manual which tells you the switches you have to pass the app in order to enable or disable certain features, like disabling ontrack format or relocating DDO when a memory manager is available.
I'm playing around with Ontrack Disk Manager 9.57 to get a 32G CF card working with my 386 build. I have DOS 6.22 so I had it configured 4 partitions of 2G each. It's working great except that I notice it reduces DOS memory by around 15k. Is this typical? Also the manual says it can relocate much of itself to UMBs with the /L=2 parameter. Has anyone ever tried this with success? It doesn't seem to do anything with my build. I do have EMM386 loaded and can load mouse or cd-rom drivers into UMBs with no issue. This is not about loading the ONTRACKD.SYS driver, but the disk overlay itself, which is loaded by MBR and before DOS I assume. Technically I would be very impressed if this is actually feasible at all. ?
I didn't realize the SIIG EIDE card I have around actually supports disks up to 8.4G. I tried it yesterday and it works great except for some reason the BIOS on this card reserve 2k from DOS. So I end up with 638K for now.
Ontrack needs to modify the MBR and write some of its data to the drive so it can get loaded to memory at boot time, that's why you're supposed to format the drive AFTER Ontrack is active and is doing the translation to access the full capacity of the disk.
ok but how do i know if it worked? its supposedly supposed to take a while to format but it formats in only a few seconds and claims to be done. it also doesn't ask for a boot disk or anything just says to restart.
as of right now with the ontrack drive empty with no windows instalation , the computer doesn't do anything at all with the drive. theres no ontrack word or logo that pops up before it tries to search for an os install
I'm not getting something here,
If the drive is recognized, working fine at full capacity and has a windows installation, then you don't need the overlay software
If the drive is wiped by installing ontrack, why don't you install windows the same way you initially installed it? How did this hard disk end up with windows on it? And no, a windows installation won't erase ontrack.
The only probable scenario I can think of is that the hdd had already windows installed while in another pc and now you want to put it on a pc for which it is too large and needs ontrack. Well in this case you'll need to reinstall everything, somehow.
The only probable scenario I can think of is that the hdd had already windows installed while in another pc and now you want to put it on a pc for which it is too large and needs ontrack. Well in this case you'll need to reinstall everything, somehow.
Ok man I guess I can help you. I have used these kind of disk utilities in the past, but I always just install windows 98 with a OEM 98se cd rom boot disk. Thats what you need.
The kind of Ontrack thing I used was a ontrack kill disk utility that was a drive wiper and it was like kill disk, the other things I used before are partition magic. I have used those ontrack drive overlays.
No matter, I used those programs for specific case rare cases, I alwasy just cam back to a 98se oem cd rom boot disk. Google it if you dont have one.
i dont know what the specs of the drive are its an 8gb dom. And ontrack doesn't seem to specify needing to set any parameters. it's being done on a machine that can already detect the dom anyway then moved to a 486
I could be completely wrong about this, but you might need to install the overlay software on the system where you intend to use it . I am not sure if it will install properly on a system whose BIOS already supports "large" disks . I would also mention that I am not sure any system will actually be able to read or write to the disk with the overlay installed, unless you either boot with from the drive where the overlay is installed or a boot floppy that has a copy of the overlay software .
It's been a long time but I have a vague memory of having to let the PC boot initially from the HDD (with ontrack installed) and then pressing/holding keys down if you need to boot a floppy, to ensure the DDO gets loaded.
But basically
Yes, set this up on the PC you intend to use it on
No, Installing windows wont undo ontracks work as long as you use its spacebar method to boot from floppy (you can see this at 6:57 in the video)
--
NetZ Computing Ltd. ISRAEL sup... resq.co.il
InVircible Anti-Virus Software, ResQdisk and Data Recovery Utilities
E-mail sent in reply to this post will not be considered private and
may be answered in the newsgroup.
It depends. If it's Disk Manager, then removing the dynamic drive overlay (DDO)
without losing the data already on the drive is not a simple task but can be
done. You'll need a disk sector editor for the purpose, good understanding of
disk structures, and guidance. The DM removal tool provided by disk producers
will also remove all your data and files from the drive, not only the boot
overlay. If what you installed is rather EZ-drive and not DM, then the removal is fairly
simple (retaining your data and files in functional state), with either a
Seagate dedicated tool, or with RESQDISK /REBUILD (www.resq.co.il/resq.php).
Read the primer on my page before attempting anything.Regards, Zvi
Thanks for the pointers... I will have to bring home some DOS sector
editor programs and have a look at the boot record (Win ME doesn't have the
"boot to DOS" option). As for which it is... The install was "Disk Wizard" by Seagate, and this
appears to be part of how they regain control after a reboot (part of the
disk data transer procedure). However, the UNINSTALL for Disk Wizard
doesn't touch it (although it did remove anything from the startup
folders). Nothing in the Autoexec or Config files either.The block lettering says "Starting ONTRACK... Disk Wizard".Wouldn't particularly matter except:
a) I don't like things in my system that I didn't intentionally put there.
b) It slows down booting (waits a while with an option to boot from
floppy).
c) It... well, it's the principle of the thing, dang it!!! tnx, jmk
35fe9a5643
0 new messages