Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Any utility to read/browse Windows NT 4.0 Backup files?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Any utility to read/browse Windows NT 4.0 Backup files?

    I've got a few tapes that start off like this:


    Code:
    00000000  54 41 50 45 00 00 00 00  00 04 0e 00 00 00 00 00  |TAPE............|
    00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    00000030  02 00 08 00 87 55 3c 2b  00 00 00 00 01 00 00 00  |.....U<+........|
    00000040  00 00 01 00 34 00 5e 00  00 00 00 00 00 00 00 00  |....4.^.........|
    00000050  80 00 92 00 00 04 be 0c  1f 46 78 ab 0f 01 54 00  |.........Fx...T.|
    00000060  61 00 70 00 65 00 20 00  63 00 72 00 65 00 61 00  |a.p.e. .c.r.e.a.|
    00000070  74 00 65 00 64 00 20 00  6f 00 6e 00 20 00 30 00  |t.e.d. .o.n. .0.|
    00000080  39 00 2f 00 32 00 38 00  2f 00 32 00 30 00 30 00  |9./.2.8./.2.0.0.|
    00000090  31 00 4d 00 69 00 63 00  72 00 6f 00 73 00 6f 00  |1.M.i.c.r.o.s.o.|
    000000a0  66 00 74 00 20 00 57 00  69 00 6e 00 64 00 6f 00  |f.t. .W.i.n.d.o.|
    000000b0  77 00 73 00 20 00 4e 00  54 00 20 00 42 00 61 00  |w.s. .N.T. .B.a.|
    000000c0  63 00 6b 00 75 00 70 00  20 00 28 00 4e 00 54 00  |c.k.u.p. .(.N.T.|
    000000d0  42 00 41 00 43 00 4b 00  55 00 50 00 2e 00 45 00  |B.A.C.K.U.P...E.|
    000000e0  58 00 45 00 29 00 20 00  56 00 65 00 72 00 73 00  |X.E.). .V.e.r.s.|
    000000f0  69 00 6f 00 6e 00 20 00  31 00 2e 00 30 00 20 00  |i.o.n. .1...0. .|
    00000100  52 00 65 00 76 00 2e 00  20 00 33 00 2e 00 34 00  |R.e.v... .3...4.|
    00000110  31 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |1...............|
    00000120  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    00000400

    Clearly, these are WT 4.0 backup images. I can find tools to browse XP and later .BKF files, but not the earlier NT 4.0 ones. Does anyone know of any documentation for the file format or tools (other than native NT 4.0 NTBACKUP) to handle these beasts?
    Reach me: vcfblackhole _at_ protonmail dot com.

    #2
    Might be Microsoft Tape Format (MTF)


    mtf - a Microsoft Tape Format reader. Contribute to KyleBruene/mtf development by creating an account on GitHub.

    Comment


      #3
      Nope--that's post NT 4.0 backup. Got it on my machine, as well as mtftar--both choke on NT 4.0 backup files after a bit.

      As a matter of fact, I can't find any documentation on ntbackup 1.0 file format. My understanding is that NTBackup for 2K could understand NT4 tapes, but the highway stops there with XP+ using something very different, based on the mtf description.
      Reach me: vcfblackhole _at_ protonmail dot com.

      Comment


        #4
        Don't quote me on this but I have a dim memory of NT4 backup being a rebadged version of Seagate Backup Exec

        Comment


          #5
          I've heard something to that effect. One tidbit is that NT4 NTBackup only backs up to tape, not disk. 2K and later can backup to disk. I do have a copy of Backup Exec, I'll probe around a bit. Could be why M$ never documented the structure. This appears to confirm your suspicion.

          Tape only, apparently
          MTF 1.00A seems to agree with the data (note the Seagate Imprimatur).
          Last edited by Chuck(G); November 29, 2021, 08:55 AM.
          Reach me: vcfblackhole _at_ protonmail dot com.

          Comment


            #6
            After trying to get mtftar to work (it goes for a bit and just stops--and the code is unreadable without a lot of aspirin), I broke down and installed Windows NT 4.0 Terminal Server (with SP3) on an old system. Some things that I observed:

            1) You can define the installation of several different tape drives and NTBackup will select the appropriate one, but you'll always get a serious event noted at login time for the drives not installed. Minor annoyance.
            2) NTFS as NT 4 understands it is not the same as NTFS as Windows 2000 knows it. I formatted a partition on a secondary hard drive with 2K and NT4 refused to see it. So reformat under NT4 and everything is cool. Minor annoyance again.
            3) MTF is wedded to the tape block size; mtftar apparently doesn't know this. Volume and set header records are single-block files, but the actual size can be all over the map, depending on the drive. For example, a Seagate TR7 drive defaults to 512 bytes, but my Quantum DLT4000 defaults to 8192. You can transfer backup volumes between different types of drives, providing that the file size is a multiple of the physical block size. To go from 1024 byte blocks to 8192 byte ones, for example, I used the linux "truncate" utility; you can use it extend a file with nulls to an even multiple of a large block by using the "-s %blocksize" argument.
            4. There seems to be an opinion that NTBackup for NT4 servers is not the same NTBackup used for NT4 workstation. It could be true, so I decided to play things safe and use NT server.

            Hope this is useful to other folks.
            Reach me: vcfblackhole _at_ protonmail dot com.

            Comment


              #7
              Basic support for NT 5.0/2000's version of NTFS (i.e. without support for its new features) was added to NT 4.0's NTFS driver in, I gather, SP4. (And there's normally no good reason to not just install SP6a.) There is also a post-SP6a hotfix that adds support for it to AUTOCHK/CHKDSK, but according to BearWindows it can sometimes cause the system to hang when checking disks. It's best to just stick with NT 4's native NTFS version, and avoid multi-booting with or otherwise directly accessing such volumes with newer Windows versions; they will automatically, surreptitiously "upgrade" NT 4 NTFS partitions.

              Note that NT Workstation, NT Server, and NT Server Enterprise Edition are all different editions (in licensing, branding, and which system utilities are included) of the same OS, and share the same service packs and many hotfixes, whereas NT Terminal Server is a specially-modified version of NT 4.0 and has its own separate versions of service packs and hotfixes. I'm not familiar with whether NT Backup is one, but certain components do enable certain features or vary in their behavior depending on whether you're running a Server or Workstation edition (e.g. Disk Administrator doesn't allow you to create fault-tolerant partition sets on Workstation, and applications can benefit from the /3GB boot.ini switch only on Enterprise Edition).

              Comment


                #8
                I threw up my hands with the backups I've got, after having run NTBackup, mtftar, mtf etc. and getting incomplete or various errors. Customer wants his data files from 20+ years ago, so I wrote my own extractor, which searches for the various DBLKs and works from there. Doesn't care about sets, tape headers, whatever--just the important stuff. You can even have a program poop in the middle of the backup file and the utilities will still grab most of the data.

                Sorry to say that it can be much easier to craft your own utilities than trying to make unknown or badly documented third-party stuff work. The bonus is that you come away with a very detailed understanding of the mechanism.

                That picture hasn't changed at all over the years. Crappy code is a plague on our civilization.
                Reach me: vcfblackhole _at_ protonmail dot com.

                Comment

                Working...
                X