1
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Don't be impatient and remember Arca Noae has limited resources but do do pretty good at fixing these kinds of things and since your hardware isn't that old, with luck they will come up with a fix but time is always a problem and expecting a fix in 2 days is asking a lot.
I see three problems here.
First, Arca Noae cannot support eCS, in any flavor. ArcaOS is a different version of OS/2, and they are only licensed to work with what is in ArcaOS, for use with ArcaOS. They can distribute drivers, that were not produced by IBM, for use with any version of OS/2.
Second, it appears that the machine is not compatible with the requirements for ArcaOS. Is it possible, that there is a BIOS setting that prevents anything from writing to track 0? If so, make sure that it is turned OFF.
If there is no setting to prevent writing to track 0, my bet is that this is not a problem with OS2DASD.DMD, but with something that loaded previously. You might try making sure that you don't use AHCI. There was a time when the first loaded (AHCI, or IDE) would take control of the controller, when there is no BIOS setting. ArcaOS, by default, loads AHCI first, when the controller is capable (but it may not work that way. Early AHCI BIOS support was not very good).
Either you'll need to create an AN support incident or hope that someone make a debug version of OS2DASD.
You can boot from a DFSee stick (or CD) and see if FreeDOS or Puppy Linux can tell more about the faulty controller.
You should be able to run disktool. If not, if you try the full DFSee, it should run and tell you a lot about the disk. I don't know of a helpful OS2DASD mode.
Did you wipe the hard drive?