DOS ain't dead

On 07 May 2016 I finished my 32-bit DOS port of dmidecode version 3.0 using DJGPP version 2.04 beta. (Yes, I know that 2.05 is out, but I didn't have enough time...)

Binaries, user manuals in ASCII format, and fully configured sources plus some simple instructions on how to rebuild are available at http://www.bttr-software.de/ports/.

---
Forum admin

> On 07 May 2016 I finished my 32-bit DOS port of dmidecode version 3.0

Mirrored!

> > On 07 May 2016 I finished my 32-bit DOS port of
> dmidecode version 3.0
>
> Mirrored!
>

Nice.
Maybe someone could test on different systems. I only tried on my ThinkPad R500 with Windows XP SP3.

---
Forum admin

> Maybe someone could test on different systems. I only tried on my ThinkPad
> R500 with Windows XP SP3.

In what way? What kind of testing? Do you want us to email you the output of specific commands?

But, honestly, I don't have that many machines to test myself anymore.

If you think announcing on SF.net or mentioning this on the freedos-* mailing lists can help, then I'll do so.

> Maybe someone could test on different systems.

rr -- thanks for the new build! When i get a new (used) system to check out, DMIDecode is usually the first tool i go for. (Keeping in mind that one can't totally rely on all DMI information stored in every computer to be completely accurate.)

Anyway, i ran the new build on five different P4 desktop systems under pure MS-DOS 7.1 -- three IBM and two Dell. All ok.

- Doug B.

Seems to work fine under MS-DOS...

---
DOS gives me freedom to unlimited HW access.

> > Maybe someone could test on different systems. I only tried on my
> ThinkPad
> > R500 with Windows XP SP3.
>
> In what way? What kind of testing? Do you want us to email you the output
> of specific commands?

No. I just wanted to make sure it runs on a broad range of DOS systems.

---
Forum admin

> Seems to work fine under MS-DOS...

Thanks for testing.

---
Forum admin

> > Maybe someone could test on different systems.
>
> rr -- thanks for the new build! When i get a new (used) system to check
> out, DMIDecode is usually the first tool i go for. (Keeping in mind that
> one can't totally rely on all DMI information stored in every computer to
> be completely accurate.)
>
> Anyway, i ran the new build on five different P4 desktop systems under pure
> MS-DOS 7.1 -- three IBM and two Dell. All ok.

Thanks for testing.

---
Forum admin

> > In what way? What kind of testing? Do you want us to email you the
> output
> > of specific commands?
>
> No. I just wanted to make sure it runs on a broad range of DOS
> systems.

I ran it (seemingly successfully) on my Dell laptop and Lenovo desktop. I didn't see any obvious errors, but then again, a lot of that "minutiae" (is that really how you spell it?) was a bit over my head. So, as far as I know, it works fine.

Hi, I get on both compilation 204 and 205, Your binary files,

"Command or filename not recognized" ...

David

> Hi, I get on both compilation 204 and 205, Your binary files,
>
> "Command or filename not recognized" ...

Please reveal more details, David.

---
Forum admin

Hi, I tried Your binary files on plain EDRDOS by Udo Kuhnt and
shell in DJGPP, in both cases I didn`t have rules to run binary
file dmidecode, it noticed "Command or filename doesn`t recognize"
I have own compilation of Your patch in djgpp205, but situation
was repeated :(

> Hi, I tried Your binary files on plain EDRDOS by Udo Kuhnt and
> shell in DJGPP, in both cases I didn`t have rules to run binary
> file dmidecode, it noticed "Command or filename doesn`t recognize"
> I have own compilation of Your patch in djgpp205, but situation
> was repeated :(

dmidecode.exe is a long filename. Try DMIDEC~1.EXE.
Is it that simple?

---
Forum admin

>
> dmidecode.exe is a long filename. Try
> DMIDEC~1.EXE.
> Is it that simple?

OK, I move dmidecode.exe to 1.exe and it works :)