Date: Tue, 24 Feb 2004 22:55:03 +0000 From: "Matt Hanson" <[EMAIL PROTECTED]> Subject: Re: [LIB] Recover files with long file names in DOS
From: Philip Nienhuis <[EMAIL PROTECTED]>
>
> Yeah... that was the URL you pointed to. I did download MHAIRU.ZIP with the
MHAIRU.ZIP? never heard of it, I'll have to visit that site again....
Bottom of the that page linked on Xin's page:
http://theinquirer.net/?article=10215
--------------------------- L'INQs Panasonic v2.06 ASPI Manager for USB mass storage USBASPI.SYS (Look for the "F2H" subdirectory after extraction of the downloaded archive) FTP site: Motto >>>Hairu<<< Mass Storage ASPI drivers <<<<< ---------------------------
I couldn't make any sense of the Japanese on the Panasonic site. And the FTP/MHairu link didn't connect. So I did a Google search for the two drivers Xin had set up for a CF connection in DOS: USBASPI.SYS & DI1000DD.SYS and came up with a bunch of sites with info on USB in DOS, and with links for downloading MHAIRU.ZIP:
http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/
(No USB device drivers needed, just the ASPI layer? weird...) So, bad luck it seems. Apparently it doesn't work. BTW, I suspect those drivers are meant more for CD-ROM / CDRW devices.
Actually Xin managed to set up a USB connection in DOS to load software onto his Panasonic CF-M32 from a CF card:
http://www.fixup.net/tips/usbdos/index.htm
"I successfully installed Windows Server 2003 Web Edition onto CF-M32 from a 512MB CF card."
But I know my USB Dazzle Zio CF reader needs its own drivers installed on a Windows system for it to be recognized. So there could be an issue there with getting things set up in DOS.
ASPI is not something I would relate with an IDE device like a CF card or a MicroDrive.
Though the Zio CF reader needs drivers in Windows, the CF cards and Microdrive I have are always recognized as soon as they're inserted into the reader, and Windows sets up drivers for them automatically as 'Generic IDE Disk TypeXX' in the 'Disk Drives' section of Device Manager. But I have no idea what might be going on in DOS.
Did you try the Panasonic drivers? kxlcb35an.exe, kxlrw31an.exe or kxlrw40an.exe? (Admittedly some command of Japanese wouldn't hurt once these are unpacked :-) But Xin has his hints.)
I’m downloading them now. Again, the Japanese web pages were a bit much for me, so I just found them on the Panasonic site via Google. kxlcb35an.exe isn’t a zip file, and wants to install to a directory. I hope these aren’t going to set themselves into the OS. Probably not. But if info files are in Japanese….
> >And Xin also mentions an
> >Addonics DOS USB driver (search for DOSboot.exe or so on Addonics, their
> >link to DOS_USB_Boot-4.4 is a 404).
>
> I couldn't find any references to USB_DOS_Driver_v4.4.zip or DOSboot.exe
> using the Addonics search engine. So I did an advanced Google search on
> their site, and came up with the download USBBoot.zip that contains a FD
> image file and rawrite.exe. Even Google didn't come up with any results
> for: USB_DOS_Driver_v4.4.zip Have't tried the image file yet.
You can also d/ld WinImage, use it to extract the relevant drivers and CONFIG.SYS & AUTOEXEC.BAT to a formatted boot floppy (i.e., floppy including system files).
‘WinImage’… I did? USBBoot.zip contains Dosboot.img, rawritre2.exe and readme.txt. I assumed rawrite2.exe would install the image to a FD.
What that means is just that you can't boot from the Lib's USB port(s). Many other computers have this same limitation. Therefore Addonics made a boot floppy allowing one to boot DOS from floppy, initialize the USB ports from that DOS and be able to use the USB ports. That has nothing to do with booting from USB; it revolves around booting from floppy and being able to use the USB ports. From what I understood from several texts on the Addonics site this DOS boot floppy with USB support was made to be able to install Windows (or any other OS) from an external USB mass storage device (e.g., Addonics CD-ROM player). Addonics is just a bit more customer-friendly than most other USB device manufacturers, in that they also think of customers with older hardware.
Actually the problem isn’t one of trying to >boot< from a USB port. From what I can remember of what I’ve read on the list, I don’t think the Libbys are ever going to do that without writing a new BIOS for them. I’m only looking at getting >access< through the USB port to send data to the Microdrive there.
So once again, just try this thing too if you want. If it fails, nothing is lost except some of your time.
Okay
But then again, I wonder what it is that you want. You asked for DOS USB support and I gave you a few hints. But I understood your actual problem as follows:
You have a, or some, fubarred hard disk partitions made originally under EZ-drive in the Libretto. Now you want to salvage as many files as possible. Because the partition scheme was made in the Lib, it is most obvious to use the HD in the Lib, so you want to boot the Lib somehow so that you can access the data, and then transfer those data to another PC or external device.
Actually, accessing the Microdrive via USB in DOS has just been a learning exercise to see if USB in DOS is possible. At this point I’ve actually gotten most of the data recovered via the Stellar Phoenix recovery software running on a desktop with the 20GB HDD from the L100 set up with a 2.5” to 3.5” IDE adapter. Phoenix found partition data for 33 logical drives, and it’s taking a bit of time to go through each one and determine which ones contain the data that was on the HDD when it got #XS%W*Ked, and which ones contain data from past installations. But yes, I’m 1st recovering what data I can, and then will play with ideas on how to repair things.
I’m convinced that if I’d gone the route of FDISK /MBR, and didn’t have recovery software, I’d never have retrieved the data on the drive. Logical drive 31 looks like it had all the data I lost. Logical drive 32 is just like the directory structure on the HDD if I boot it in the L100 from a startup FD, go to the E: drive where that data used to be, and do a DIR to list the folders on the root. That gives me a corrupted file structure that matches what Phoenix reported as Logical drive 32. And 32 was only had part of what I had, that Logical drive 31 seems to match. Interesting that #32 contains some folders and files from another incarnation of the drive from past Libretto installation.
What caused further corruption to the drive after the initial problems ghosting an image, was my attempts to size that last E: drive down more. I had shrunk it down to make room for the image. When I sized E: down even more after the Ghost problem, Partition Magic failed and aborted with errors. So that accounts for some of the data for the last logical drives Phoenix has found, 30, 31, 32, and 33.
Using some external USB device is one good way to get it together. Problem however is the long file names, that will work only if Windows itself is running on the Libretto. So, the DOS USB option by itself may not be the best way to get where you want.
Actually I’ve ironed out the long file name in DOS problem. I found 2 websites that solved the problem:
Dos Interlink: http://www.pcxt-micro.com/Dos_Interlink.html
That site shows you how to use the old DOS files INTERLNK.EXE and INTERSVR.EXE to set up a cable connection in DOS for transferring files.
LFN Tools http://www.odi.ch/prog/lfn/index.php
The archive file lfn-en.zip there includes Lcopy.exe. And with a bit of wrestling, it copies files and nested folders over to another drive retaining the long file names. It drove me crazy when it kept reporting it couldn’t fine the source or destination files or folders. But I finally discovered that Lcopy doesn’t recognize paths with a tilde ~. You have to quote the entire path. But it works well. At this point I don’t think I’ll need to go this route to recover my data, as Phoenix seems to have done the job. But I can’t say it was faster, as Phoenix needs a couple hours on a PII 450 to scan the entire 20GB HDD. And then it scans the logical drives again after that. A newer system would be nice!
But another route for the DOS Lcopy method, and a faster one might be via getting a NIC card working in DOS. Linksys support told me that my Etherfast NIC isn’t supported in DOS. But I haven’t looked at the possibility of getting my Xicom combo card going in DOS. Another day…
I guess you need to find a way to boot Windows on your Libretto. As from your other posts I inferred that you already saved the data from the other two partitions, maybe you should just reinstall a bare Windows on C: without it touching the partitioning scheme (under EZ-drive).
That would have wiped out the data on the existing C: partition.
With a little luck and playing around with the tools suggested by many other people who posted replies you might be able to access the fubarred partition again.
Does this help?
Si… bueno!
Anyone know which WWII era acronym the term fubar is derived from? ;-P And how it came to be used in reference to computers in the 60s?
Matt
_________________________________________________________________
Get fast, reliable access with MSN 9 Dial-up. Click here for Special Offer! http://click.atdmt.com/AVE/go/onm00200361ave/direct/01/
************************************************************** http://libretto.basiclink.com - Libretto mailing list http://www.silverace.com/libretto/ - Archives
-------TO UNSUBSCRIBE-------
Reply to any of the list messages. The reply mail should be
addressed to: [EMAIL PROTECTED] - Then replace any text
on the message's subject line: cmd:unsubscribe
--------TO UNSUBSCRIBE DIGEST------
Do above but with this on subject line: cmd:unsubscribe digest
**************************************************************