1.

Solve : HP150 Touch Screen (1983) diskettes?

Answer»

I have some diskettes that have data and programs from an old HP150.
Is there anything other than an HP150 disk drive that can read the data from them?
I have a few computers ranging from Windows XP to whatever dos version from 1993 and neither of them will read the DISKS.Are the diskettes write protected?They appear not to be write-protected.Read this:

http://fixunix.com/hewlett-packard/102279-old-hp150-read-diskettes-problem.htmlThat's close but not quite the problem. My problem is that my PC, even in DOS mode doesn't recoginze the diskette at all. When I try the command "dir", it beeps and prints nonsensical characters.

I think the disks may have a FAT-12 file system or a FAT-16. Do I need a special driver to view the data on my Windows XP?This is the error message I get:

"The volume does not contain a recognized file system.
Please make sure that all required file system drivers are loaded and that the v
olume is not corrupted."It looks like DOS used on that computer was not real MS-DOS, and this may be your problem...
http://en.wikipedia.org/wiki/HP-150
Quote

The HP-150, a "compact, powerful and innovative" computer made by Hewlett-Packard in 1983 and based on the Intel 8088, was one of the world's earliest commercialized touch screen computers. The machine was not IBM PC compatible, although it was MS-DOS compatible. Customized MS-DOS VERSIONS 2.01, 2.11 and 3.20 were available.
The PAPERWORK for the HP-150 said it used MS-DOS 2.11Well, Wikipedia SAYS, it was some customized version of MSDOS.Try it on a machine that is running an official install of DOS 6.22.......

Command Prompt /DOS mode ceased being DOS after Win98SE.OK. I'll give that a shot. I just found out, though, that the HP150 was not IBM compatible so I may be out of luck.Doesn't matter...the file system and OS is all that matters here. Or should i will say.I found the answer- the media descriptor byte was incorrect. I had to get a disk editor to show the sectors and replace the media descriptor byte with the correct one and then my computer had no problem reading it.

Thanks for your help. I learned a great deal of stuff that I didn't know before.Good going


Discussion

No Comment Found