Bug with GDM2k - MDOS 7.45 - IDE

[+dhe]

@F.G. Kaal

 

I had:

 SCSMAP 1A

 SCSMAP 2B

 ASSIGN E=SCS1:

 ASSIGN F=SCS2:

 with ide controller.

 

  I was using GDM2K 3.7 and MDOS 7.45 to move directories from E: > F:

 

  The first few directories went fine, then on the 4th directory, the copy started, and I received an error and the copy halted, at what looked like the delete phase of the move.

  I didn't take a picture of that.

 

  I rebooted, when I did, all the files, beneath the directory I was moving "KAAL" are gone, replaced with the picture below.

  I can't remove the individual files, so I guess I need to reformat the partition.

 

  What's the procedure for formatting an IDE Partition on MDOS?

 

 

 

 

 

[+9640News]

MDOS does not format HFDC's, IDE's, SCSI's, or HRD's.  There are various 4A and in some cases, Geneve utilities to allow formatting hard drive type interface formats.

 

For the IDE, use Fred Kaal's program DU2K in the GPL interpreter.  I don't know if his latest version is "Geneve aware", so you might need to use rompage mode.

 

As far as your issue for copying/moving files you had, if you can duplicate the problem  and then confirm in in MAME as well, then please provide instructions and a source file to duplicate the problem and we can investigate.  Neither Tim nor I have an IDE controller and all testing was done on MAME.

 

Assuming you used DU2K to originally format the IDE drives, did you use the newer DSR or older DSR for the IDE card?

 

Were you copying?  Or were you moving files?  Was it just the destination drive with issues?  If copying, then the source should not have been a problem. What was the size of the IDE drive?

 

 

[+dhe]

    Hi Beery,

      I didn't setup the system, Shift838 did for me, I got the card about a year ago, before the recent DSR release, so probably a 1.X DSR, which probably shouldn't be an issue, as it's my understanding the DSR is just used to load the DSR.

 

     I really wasn't tracking all the details because I wasn't working to make a bug report, simply moving some directories from one partition "drive letter assignment"  to another.

 

 

 

[+dhe]

I figured out who to use DU2K.

I was able to initalize the four ide partitions,

    SCSMAP 1A - Which put the first part as SCS1.

    I then copied AUTOEXEC, LOAD-IDE AND SYSTEM-SYS.

     I see a blip, as it hits the IDE card and then totally locks up.

 

[+9640News]

12 minutes ago, dhe said:

I figured out who to use DU2K.

I was able to initalize the four ide partitions,

    SCSMAP 1A - Which put the first part as SCS1.

    I then copied AUTOEXEC, LOAD-IDE AND SYSTEM-SYS.

     I see a blip, as it hits the IDE card and then totally locks up.

 

Is the IDE at >1200?

 

Have you previously been able to boot from the IDE?

 

I probably will not be online after this post until Monday as I am leaving from work to go camping/flying tomorrow afternoon and will be getting in very late Sunday.

[+9640News]

I just thought of something else.  Make sure with DU2K the drive you are placing those files are on IDE1, not IDE2.  LOAD-IDE is unaware of any mapping you may have done as SCSMAP is part of MDOS after it is loaded, nothing prior.

[+InsaneMultitasker]

1 hour ago, dhe said:

I didn't setup the system, Shift838 did for me, I got the card about a year ago, before the recent DSR release, so probably a 1.X DSR, which probably shouldn't be an issue, as it's my understanding the DSR is just used to load the DSR.

This is incorrect.  The Geneve OS and its DSR call the IDE DSR read/write sector routine (>80) for all operations.  This approach keeps the low-level routines within Fred's DSR, allowing MDOS to manage the file system without needing to know about the hardware nor the partitions.  A corrupt or outdated IDE DSR is not a good thing. 

[+dhe]

8 hours ago, 9640News said:

Is the IDE at >1200?

 

Have you previously been able to boot from the IDE?

I think the card was set at >1900 or >1600.

As stated above, card was booting and working, as it came from @Shift838.

During a *MOVE* directory from one partition to another is when everything fell apart.

Prior MOVE directories with GDM2K had worked.

 

Look at the date line for the DSR, I'm pretty sure I had DSR 1.5 in place.

 

My next attempt is to turn the card switch to disable.

 

Get a boot, enable the card, load IDELOAD and see if I can load DSR 1.6.

 

If that works, load DU2K and try a fresh partition and initialization.

 

What CRU address do you recommend?

Because of remap issues, I do believe IDE2 or partition2 also had a copy of system-sys and load-ide, in addition to partition 1.

 

 

[+dhe]

@9640News @F.G. Kaal

 

Beery,

 The CRU is at >1900.
 

 It appears Initalizing the four partitions allows boot from TIPI.

 I think I want to try upgrading the DSR to 16 before I try to boot again from IDE.

 

 Q: Is >1900 the correct CRU?

 

 

[+dhe]

 

IDE DSR 16 loaded.

 

 

[+dhe]

Copied load-ide and system-sys to the root of ide and booted twice - major improvement over system just locking up.

 

@9640News

Some question about the loading of autoexec.
Autoexec is always loaded off the boot device?
  If no autoexec on the boot device, will it look for an autoexec on dsk1?

SCSMAP 1A           remaps the name scs1 to ide device 1
SCSMAP 2B           remaps the name scs2 to ide device 2
SCSMAP 3C           remaps the name scs3 to ide device 3

Can I assign any letter to any device name?
Can I assign a to scs1?

ASSIGN E=SCS1:      
ASSIGN F=SCS2:
ASSIGN G=SCS3:
ASSIGN I=TIP1:

 

[+dhe]

@9640News question about the bootv2 EPROM.

 

I've read the docs, and I don't see that it answers my question.

 

My question is, if you have multiple boot devices - in my case a TIPI, and IDE and a floppy disk, each contains the proper load-* for the devices and system-sys (floppy not needing a load-*).  What order are the devices searched for booting?

[Shift838]

11 hours ago, dhe said:

@9640News question about the bootv2 EPROM.

 

I've read the docs, and I don't see that it answers my question.

 

My question is, if you have multiple boot devices - in my case a TIPI, and IDE and a floppy disk, each contains the proper load-* for the devices and system-sys (floppy not needing a load-*).  What order are the devices searched for booting?

If I recall, the new boot eprom v2 searches to boot in the below order if cards are present:

 

1. HFDC (hard disk)

2. SCSI

3. IDE

4. TiPi

5. Floppy

 

I could be wrong, but I think I remember it doing it that way.

 

Also, for the autoexec file to load it always looks to where you have it set to for CYA, i don't think if it does not find it, MDOS will default to say floppy disk, it just will not look for it any longer.  Tim or Beery will need to verify.

[+InsaneMultitasker]

@dhe and @Shift838 

You can hold the DEL key when the OS starts to force autoexec to load from Dsk1.  If this no longer works in the unmodified release and/or the CYA patched OS, then we need to fix that feature. 
 

With the EPROM and an unmodified OS, the autoexec will load from the boot device.  This is controlled by a flag in the loader (load-ide, for example) and a bit of code in the OS.  
 

With PFM, the autoexec location is typically set via CYA.  I suppose that I could code the PFM to set a boot flag, similar to the EPROM, as an alternative.  
 

CYA overrides the default location, to ensure the OS always loads autoexec from the same location during a warm restart.  Thinking about this now, what probably should be done is to save the boot flag and then use that device/location for subsequent warm reboots initiated by ctrl-alt-del.