DOS ain't dead

CHM reader in DOS (Announce)

posted by marcov, 26.03.2009, 17:51

> If I knew I would fix it. I suspect a problem in the tabel formatting
> routine, something like a var that is not reinitialized. However the
> problem drifts, and the exception is hard to trace back to the corruption
> that caused it.

(I should have mentioned that it does this too in 64-bit mode, where it can allocate +/- 6GB, so it is not memory fragmentation or the like)

Complete thread:

• CHM reader in DOS - Laaca, 21.03.2009, 08:57 (Announce)
  • CHM reader in DOS - DOS386, 22.03.2009, 05:42
    • CHM reader in DOS - marcov, 23.03.2009, 17:22
      • CHM reader in DOS - DOS386, 31.03.2009, 03:47
  • CHM reader in DOS - marcov, 23.03.2009, 17:21
    • CHM reader in DOS - Laaca, 23.03.2009, 18:43
      • CHM reader in DOS - marcov, 23.03.2009, 21:30
        • CHM reader in DOS - marcov, 26.03.2009, 17:51
          • CHM reader in DOS - Rugxulo, 01.04.2009, 13:27
            • CHM reader in DOS - marcov, 01.04.2009, 23:39
              • CHM reader in DOS - Rugxulo, 02.04.2009, 00:16
                • CHM reader in DOS - marcov, 02.04.2009, 10:35
                  • big RAM / 64-bit / etc. - Rugxulo, 02.04.2009, 21:19
                    • big RAM / 64-bit / etc. - marcov, 04.04.2009, 15:13
                      • big RAM / 64-bit / etc. - Rugxulo, 04.04.2009, 17:21
                        • big problem ??? RAM / 64-bit / etc. - DOS386, 05.04.2009, 04:27
                          • big problem ??? RAM / 64-bit / etc. - marcov, 06.04.2009, 10:04
                            • big problem ??? RAM / 64-bit / etc. - DOS386, 07.04.2009, 04:32
                              • big problem ??? RAM / 64-bit / etc. - marcov, 07.04.2009, 13:24
                                • big problem ??? RAM / 64-bit / etc. - Rugxulo, 07.04.2009, 13:42
                        • big RAM / 64-bit / etc. - marcov, 06.04.2009, 09:53
                          • big RAM / 64-bit / etc. - Rugxulo, 07.04.2009, 00:43