Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!sgi!wdl1!bobw From: bobw@wdl1.UUCP (Robert Lee Wilson Jr.) Newsgroups: comp.sys.ibm.pc Subject: restore problem, 3.2 vs 3.3? Message-ID: <4160009@wdl1.UUCP> Date: 19 Aug 88 17:14:08 GMT Article-I.D.: wdl1.4160009 Lines: 37 I recently moved from MSDOS 3.2 to 3.3. At the same time I was changing from a 20MB Ampex disk to a Maxtor 1140. I carefully did a backup of the old disk, on 1.2MB 5 1/4 inch floppies.I had checked the 3.3 manuals which said that, although 3.3 backup can't be read by 3.2 restore, it would work the way I was doing it! (All of this on a no-name AT clone...) After formatting the new disk and installing 3.3, I tried to restore the 14 disks, named by backup as 01 through 14 and so labeled by me. Restore asked me to insert disk 01, which sounded like we were going great. It quickly skipped over that and asked for disk 00, which backup had never mentioned! I tried disk 02 (write protected!). I got a message that this disk was out of sequence, but that it would be glad to continue if I would hit a key. I did. The bottom line: After each disk this repeated. At the end of the deck, restore reported that it could find no files to bring in. I had asked for *.*. I was able to get out of this fairly easily. I just added the old disk as a second physical drive and xcopy'ed the files I wanted, and of course it was fast and didn't require floppy swapping. I.e., I was lucky. What if I had not been changing disks but had just reformatted my old drive?? Is there a real problem here, that is an incompatibility between 3.2 backup and 3.3 restore, or have I just made some obvious error? I don't have an MSDOS system or manuals or my notes here at the office, but as I recall the restore command I originally gave was restore a: c:*.* /s I eventually tried a number of variations, including adding dates to say bring in everything before next year, and so on. I would be interested in this for my curiosity, but it might be very important to someone else who didn't have my easy out! Thanks for any answers, Bob Wilson at Ford Aerospace (bobw@ford-wdl1.arpa) (Of course the usual disclaimer...)