File Recovery FAT32

数据恢复原理与5款实用工具评测 数据恢复是计算机存储领域的重要技术,其核心原理基于文件系统的延迟擦除机制。当文件被删除时,操作系统仅移除文件索引而非实际数据,这使得专业工具能够扫描磁盘物理位置找回文件。这项技术在误删恢复、格式化还原等场景具有重要价值,尤其对照片、文档等数字资产保护至关重要。本文重点评测了Disk Drill、Recuva等5款主流恢复工具,涵盖从轻量级到专业级的解决方案。针对SSD的TRIM机制和HDD的不同特性,合理选择工具能显著提升恢复成功率。 阅读详情

Lab 4: File Recovery

Introduction

FAT has been around for nearly 50 years. Because of its simplicity, it is the

most widely compatible fi le system. Although recent computers have

adopted newer fi le systems, FAT32 (and its variant, exFAT) is still dominant

in SD cards and USB fl ash drives due to its compatibility.

Have you ever accidentally deleted a fi le? Do you know that it could be

recovered?In this lab, you will build a FAT32 fi le recovery tool called Need

You to Undelete my FILE, or nyufile for short.

Objectives

Through this lab, you will:

Learn the internals of the FAT32 fi le system.

Learn how to access and recover fi les from a raw disk.

Get a better understanding of key fi le system concepts.

Be a better C programmer. Learn how to write code that manipulates

data at the byte level and understand the alignment issue.

Overview

In this lab, you will work on the data stored in the FAT32 fi le system

directly, without the OS fi le system support. You will implement a tool that

recovers a deleted file specifi ed by the user.

For simplicity, you can assume thatthe deleted fi le is in the root directory.

Therefore, you don t need to search subdirectories.

 Lab 4: File Recovery

 1/18

Working with a FAT32 disk image

Before going through the details of this lab, let s first create a FAT32 disk

image. Follow these steps:

Step 1: create an empty file of a certain size

On Linux, /dev/zero is a special fi le that provides as many \0 as are read

from it. The dd command performs low-level copying of raw data.

Therefore, you can use it to generate an arbitrary-size fi le full of zeros.

For example, to create a 256KB empty fi le named fat32.disk :

[root@... cs202]# dd if=/dev/zero of=fat32.disk bs=256k count=1

Read man dd for its usage. You will use this fi le as the disk image.

Step 2: format the disk with FAT32

You can use the mkfs.fat command to create a FAT32 fi le system. The most

basic usage is:

[root@... cs202]# mkfs.fat -F 32 fat32.disk

(You can ignore the warning of not enough clusters.)

You can specify a variety of options. For example:

[root@... cs202]# mkfs.fat -F 32 -f 2 -S 512 -s 1 -R 32 fat32.disk

Here are the meanings of each option:

-F : type of FAT (FAT12, FAT16, or FAT32).

 Lab 4: File Recovery

 2/18

-f : number of FATs.

-S : number of bytes per sector.

-s : number of sectors per cluster.

-R : number of reserved sectors.

Step 3: verify the file system information

The fsck.fat command can check and repair FAT fi le systems. You can

invoke it with -v to see the FAT details. For example:

[root@... cs202]# fsck.fat -v fat32.disk

fsck.fat 4.1 (2017-01-24)

Checking we can access the last sector of the filesystem

Warning: Filesystem is FAT32 according to fat_length and fat32_length fields,

 but has only代 写File Recovery FAT32   472 clusters, less than the required minimum of 65525.

 This may lead to problems on some systems.

Boot sector contents:

System ID "mkfs.fat"

Media byte 0xf8 (hard disk)

 512 bytes per logical sector

 512 bytes per cluster

 32 reserved sectors

First FAT starts at byte 16384 (sector 32)

 2 FATs, 32 bit entries

 2048 bytes per FAT (= 4 sectors)

Root directory start at cluster 2 (arbitrary size)

Data area starts at byte 20480 (sector 40)

 472 data clusters (241664 bytes)

32 sectors/track, 64 heads

 0 hidden sectors

 512 sectors total

Checking for unused clusters.

Checking free cluster summary.

fat32.disk: 0 files, 1/472 clusters

You can see that there are 2 FATs, 512 bytes per sector, 512 bytes per

cluster, and 32 reserved sectors. These numbers match our specifi ed

options in Step 2. You can try different options yourself.

 Lab 4: File Recovery

 3/18

Step 4: mount the file system

You can use the mount command to mount a fi le system to a mount point.

The mount point can be any empty directory. For example, you can create

one at /mnt/disk :

[root@... cs202]# mkdir /mnt/disk

Then, you can mount fat32.disk at that mount point:

[root@... cs202]# mount fat32.disk /mnt/disk

Step 5: play with the file system

After the fi le system is mounted, you can do whatever you like on it, such as

creating fi les, editing fi les, or deleting fi les. In order to avoid the hassle of

having long fi lenames in your directory entries, it is recommended that you

use only 8.3 fi lenames, which means:

The fi lename contains at most eight characters, followed optionally by a

. and at most three more characters.

The fi lename contains only uppercase letters, numbers, and the

following special characters: ! # $ % & ' ( ) - @ ^ _ ` { } ~ .

For example, you can create a fi le named HELLO.TXT :

[root@... cs202]# echo "Hello, world." > /mnt/disk/HELLO.TXT

[root@... cs202]# mkdir /mnt/disk/DIR

[root@... cs202]# touch /mnt/disk/EMPTY

For the purpose of this lab, after you write anything to the disk, make sure

to fl ush the fi le system cache using the sync command:

 Lab 4: File Recovery

 4/18

[root@... cs202]# sync

(Otherwise, if you create a fi le and immediately delete it, the fi le may not be

written to the disk at all and is unrecoverable.)

Step 6: unmount the file system

When you fi nish playing with the fi le system, you can unmount it:

[root@... cs202]# umount /mnt/disk

Step 7: examine the file system

You can examine the fi le system using the xxd command. You can specify a

range using the -s (starting offset) and -l (length) options.

For example, to examine the root directory:

[root@... cs202]# xxd -s 20480 -l 96 fat32.disk

00005000: 4845 4c4c 4f20 2020 5458 5420 0000 0000 HELLO TXT ....

00005010: 6e53 6e53 0000 0000 6e53 0300 0e00 0000 nSnS....nS......

00005020: 4449 5220 2020 2020 2020 2010 0000 0000 DIR .....

00005030: 6e53 6e53 0000 0000 6e53 0400 0000 0000 nSnS....nS......

00005040: 454d 5054 5920 2020 2020 2020 0000 0000 EMPTY ....

00005050: 6e53 6e53 0000 0000 6e53 0000 0000 0000 nSnS....nS......

(It s normal that the bytes containing timestamps are different from the

example above.)

To examine the contents of HELLO.TXT :

[root@... cs202]# xxd -s 20992 -l 14 fat32.disk

0005200: 4865 6c6c 6f2c 2077 6f72 6c64 2e0a Hello, world..

 Lab 4: File Recovery

 5/18

Note that the offsets may vary depending on how the fi le system is

formatted.

Your tasks

Important: before running your nyufile program, please make sure that

your FAT32 disk is unmounted.

Milestone 1: validate usage

There are several ways to invoke your nyufile program. Here is its usage:

[root@... cs202]# ./nyufile

Usage: ./nyufile disk <options>

 -i Print the file system information.

 -l List the root directory.

 -r filename [-s sha1] Recover a contiguous file.

 -R filename -s sha1 Recover a possibly non-contiguous file.

The fi rst argument is the fi lename of the disk image. After that, the options

can be one of the following:

-i

-l

-r filename

-r filename -s sha1

-R filename -s sha1

You need to check if the command-line arguments are valid. If not, your

program should print the above usage information verbatim and exit.

Milestone 2: print the file system information

If your nyufile program is invoked with option -i , it should print the

following information about the FAT32 fi le system:

 Lab 4: File Recovery

 6/18

Number of FATs;

Number of bytes per sector;

Number of sectors per cluster;

Number of reserved sectors.

Your output should be in the following format:

[root@... cs202]# ./nyufile fat32.disk -i

Number of FATs = 2

Number of bytes per sector = 512

Number of sectors per cluster = 1

Number of reserved sectors = 32

For all milestones, you can assume that nyufile is invoked while the disk is

unmounted.

Milestone 3: list the root directory

If your nyufile program is invoked with option -l , it should list all valid

entries in the root directory with the following information:

Filename. Similar to /bin/ls -p , if the entry is a directory, you should

append a / indicator.

File size if the entry is a fi le (not a directory).

Starting cluster if the entry is not an empty fi le.

You should also print the total number of entries at the end. Your output

should be in the following format:

[root@... cs202]# ./nyufile fat32.disk -l

HELLO.TXT (size = 14, starting cluster = 3)

DIR/ (starting cluster = 4)

EMPTY (size = 0)

Total number of entries = 3

Here are a few assumptions:

 Lab 4: File Recovery

 7/18

You should not list entries marked as deleted.

You don t need to print the details inside subdirectories.

For all milestones, there will be no long fi lename (LFN) entries. (If you

have accidentally created LFN entries when you test your program,

don t worry. You can just skip the LFN entries and print only the 8.3

fi

lename entries.)

Any fi le or directory, including the root directory, may span more than

one cluster.

There may be empty fi les.

Milestone 4: recover a small file

If your nyufile program is invoked with option -r filename , it should

recover the deleted file with the specifi ed name. The workfl ow is better

illustrated through an example:

 Lab 4: File Recovery

 8/18

[root@... cs202]# mount fat32.disk /mnt/disk

[root@... cs202]# ls -p /mnt/disk

DIR/ EMPTY HELLO.TXT

[root@... cs202]# cat /mnt/disk/HELLO.TXT

Hello, world.

[root@... cs202]# rm /mnt/disk/HELLO.TXT

rm: remove regular file '/mnt/disk/HELLO.TXT'? y

[root@... cs202]# ls -p /mnt/disk

DIR/ EMPTY

[root@... cs202]# umount /mnt/disk

[root@... cs202]# ./nyufile fat32.disk -l

DIR/ (starting cluster = 4)

EMPTY (size = 0)

Total number of entries = 2

[root@... cs202]# ./nyufile fat32.disk -r HELLO

HELLO: file not found

[root@... cs202]# ./nyufile fat32.disk -r HELLO.TXT

HELLO.TXT: successfully recovered

[root@... cs202]# ./nyufile fat32.disk -l

HELLO.TXT (size = 14, starting cluster = 3)

DIR/ (starting cluster = 4)

EMPTY (size = 0)

Total number of entries = 3

[root@... cs202]# mount fat32.disk /mnt/disk

[root@... cs202]# ls -p /mnt/disk

DIR/ EMPTY HELLO.TXT

[root@... cs202]# cat /mnt/disk/HELLO.TXT

Hello, world.

For all milestones, you only need to recover regular fi les (including empty

fi

les, but not directory fi les) in the root directory. When the fi le is

successfully recovered, your program should print

filename: successfully recovered (replace filename with the actual fi le

name).

For all milestones, you can assume that no other fi les or directories are

created or modifi ed since the deletion of the target fi le. However, multiple

fi

les may be deleted.

Besides, for all milestones, you don t need to update the FSINFO structure

because most operating systems don t care about it.

 Lab 4: File Recovery

 9/18

Here are a few assumptions specifi cally for Milestone 4:

The size of the deleted file is no more than the size of a cluster.

At most one deleted directory entry matches the given fi lename. If no

such entry exists, your program should print filename: file not found

(replace filename with the actual fi le name).

Milestone 5: recover a large contiguously-allocated file

Now, you will recover a fi le that is larger than one cluster. Nevertheless, for

Milestone 5, you can assume that such a fi le is allocated contiguously. You

can continue to assume that at most one deleted directory entry matches

the given fi lename. If no such entry exists, your program should print

filename: file not found (replace filename with the actual fi le name).

Milestone 6: detect ambiguous file recovery requests

In Milestones 4 and 5, you assumed that at most one deleted directory

entry matches the given fi lename. However, multiple fi les whose names

differ only in the fi rst character would end up having the same name when

deleted. Therefore, you may encounter more than one deleted directory

entry matching the given fi lename. When that happens, your program

should print filename: multiple candidates found (replace filename with the

actual fi le name) and abort.

This scenario is illustrated in the following example:

[root@... cs202]# mount fat32.disk /mnt/disk

[root@... cs202]# echo "My last name is Tang." > /mnt/disk/TANG.TXT

[root@... cs202]# echo "My first name is Yang." > /mnt/disk/YANG.TXT

[root@... cs202]# sync

[root@... cs202]# rm /mnt/disk/TANG.TXT /mnt/disk/YANG.TXT

rm: remove regular file '/mnt/disk/TANG.TXT'? y

rm: remove regular file '/mnt/disk/YANG.TXT'? y

[root@... cs202]# umount /mnt/disk

[root@... cs202]# ./nyufile fat32.disk -r TANG.TXT

TANG.TXT: multiple candidates found

 Lab 4: File Recovery

 10/18

Milestone 7: recover a contiguously-allocated file with

SHA-1 hash

To solve the aforementioned ambiguity, the user can provide a SHA-1 hash

via command-line option -s sha1 to help identify which deleted directory

entry should be the target fi le.

In short, a SHA-1 hash is a 160-bit fi ngerprint of a fi le, often represented as

40 hexadecimal digits. For the purpose of this lab, you can assume that

identical fi les always have the same SHA-1 hash, and different fi les always

have vastly different SHA-1 hashes. Therefore, even if multiple candidates

are found during recovery, at most one will match the given SHA-1 hash.

This scenario is illustrated in the following example:

[root@... cs202]# ./nyufile fat32.disk -r TANG.TXT -s c91761a2cc1562d36585614c

TANG.TXT: successfully recovered with SHA-1

[root@... cs202]# ./nyufile fat32.disk -l

HELLO.TXT (size = 14, starting cluster = 3)

DIR/ (starting cluster = 4)

EMPTY (size = 0)

TANG.TXT (size = 22, starting cluster = 5)

Total number of entries = 4

When the fi le is successfully recovered with SHA-1, your program should

print filename: successfully recovered with SHA-1 (replace filename with the

actual fi le name).

Note that you can use the sha1sum command to compute the SHA-1 hash of

a fi le:

[root@... cs202]# sha1sum /mnt/disk/TANG.TXT

c91761a2cc1562d36585614c8c680ecf5712e875 /mnt/disk/TANG.TXT

 Lab 4: File Recovery

 11/18

Also note that it is possible that the fi le is empty or occupies only one

cluster. The SHA-1 hash for an empty fi le is

da39a3ee5e6b4b0d3255bfef95601890afd80709 .

If no such fi le matches the given SHA-1 hash, your program should print

filename: file not found (replace filename with the actual fi le name). For

example:

[root@... cs202]# ./nyufile fat32.disk -r TANG.TXT -s 0123456789abcdef01234567

TANG.TXT: file not found

The OpenSSL library provides a function SHA1() , which computes the SHA-

1 hash of d[0...n-1] and stores the result in md[0...SHA_DIGEST_LENGTH-1] :

#include <openssl/sha.h>

#define SHA_DIGEST_LENGTH 20

unsigned char *SHA1(const unsigned char *d, size_t n, unsigned char *md);

You need to add the linker option -lcrypto to link with the OpenSSL library.

Milestone 8: recover a non-contiguously allocated file

Finally, the clusters of a fi le are no longer assumed to be contiguous. You

have to try every permutation of unallocated clusters on the fi le system in

order to fi nd the one that matches the SHA-1 hash.

The command-line option is -R filename -s sha1 . The SHA-1 hash must be

given.

Note that it is possible that the fi le is empty or occupies only one cluster. If

so, -R behaves the same as -r , as described in Milestone 7.

 Lab 4: File Recovery

 12/18

For Milestone 8, you can assume that the entire fi le is within the fi rst 20

clusters, and the fi le content occupies no more than 5 clusters, so a brute?force search is feasible.

If you cannot fi nd a fi le that matches the given SHA-1 hash, your program

should print filename: file not found (replace filename with the actual fi le

name).

FAT32 data structures

For your convenience, here are some data structures that you can copy and

paste. Please refer to the lecture slides and FAT: General Overview of On?Disk Format for details on the FAT32 fi le system layout.

 Lab 4: File Recovery

 13/18

Boot sector

#pragma pack(push,1)

typedef struct BootEntry {

 unsigned char BS_jmpBoot[3]; // Assembly instruction to jump to boot co

 unsigned char BS_OEMName[8]; // OEM Name in ASCII

 unsigned short BPB_BytsPerSec; // Bytes per sector. Allowed values includ

 unsigned char BPB_SecPerClus; // Sectors per cluster (data unit). Allowe

 unsigned short BPB_RsvdSecCnt; // Size in sectors of the reserved area

 unsigned char BPB_NumFATs; // Number of FATs

 unsigned short BPB_RootEntCnt; // Maximum number of files in the root dir

 unsigned short BPB_TotSec16; // 16-bit value of number of sectors in fi

 unsigned char BPB_Media; // Media type

 unsigned short BPB_FATSz16; // 16-bit size in sectors of each FAT for 

 unsigned short BPB_SecPerTrk; // Sectors per track of storage device

 unsigned short BPB_NumHeads; // Number of heads in storage device

 unsigned int BPB_HiddSec; // Number of sectors before the start of p

 unsigned int BPB_TotSec32; // 32-bit value of number of sectors in fi

 unsigned int BPB_FATSz32; // 32-bit size in sectors of one FAT

 unsigned short BPB_ExtFlags; // A flag for FAT

 unsigned short BPB_FSVer; // The major and minor version number

 unsigned int BPB_RootClus; // Cluster where the root directory can be

 unsigned short BPB_FSInfo; // Sector where FSINFO structure can be fo

 unsigned short BPB_BkBootSec; // Sector where backup copy of boot sector

 unsigned char BPB_Reserved[12]; // Reserved

 unsigned char BS_DrvNum; // BIOS INT13h drive number

 unsigned char BS_Reserved1; // Not used

 unsigned char BS_BootSig; // Extended boot signature to identify if 

 unsigned int BS_VolID; // Volume serial number

 unsigned char BS_VolLab[11]; // Volume label in ASCII. User defines whe

 unsigned char BS_FilSysType[8]; // File system type label in ASCII

} BootEntry;

#pragma pack(pop)

 Lab 4: File Recovery

 14/18

Directory entry

#pragma pack(push,1)

typedef struct DirEntry {

 unsigned char DIR_Name[11]; // File name

 unsigned char DIR_Attr; // File attributes

 unsigned char DIR_NTRes; // Reserved

 unsigned char DIR_CrtTimeTenth; // Created time (tenths of second)

 unsigned short DIR_CrtTime; // Created time (hours, minutes, seconds)

 unsigned short DIR_CrtDate; // Created day

 unsigned short DIR_LstAccDate; // Accessed day

 unsigned short DIR_FstClusHI; // High 2 bytes of the first cluster addre

 unsigned short DIR_WrtTime; // Written time (hours, minutes, seconds

 unsigned short DIR_WrtDate; // Written day

 unsigned short DIR_FstClusLO; // Low 2 bytes of the first cluster addres

 unsigned int DIR_FileSize; // File size in bytes. (0 for directories)

} DirEntry;

#pragma pack(pop)

Compilation

We will grade your submission in an x86_64 Rocky Linux 8 container on

Gradescope. We will compile your program using gcc 12.1.1 with the C17

standard and GNU extensions.

You must provide a Makefile , and by running make , it should generate an

executable fi le named nyufile in the current working directory. Note that

you need to add LDFLAGS=-lcrypto to your Makefile . (Refer to Lab 1 for an

example of the Makefile .)

Testing

To get started with testing, you can download a sample FAT32 disk and

expand it with the following command:

[root@... cs202]# unxz fat32.disk.xz

 Lab 4: File Recovery

 15/18

There are a few fi les on this disk:

HELLO.TXT C a small text fi le.

DIR C an empty directory.

EMPTY.TXT C an empty fi le.

CONT.TXT C a large contiguously-allocated file.

NON_CONT.TXT C a large non-contiguously allocated file.

You should make your own test cases and test your program thoroughly.

Make sure to test your program with disks formatted with different

parameters.

The autograder

We are providing a sample autograder with a few test cases. Please extract

them in your Docker container and follow the instructions in the README

fi

le. (Refer to Lab 1 for how to extract a .tar.xz fi le.)

Note that the test cases are not exhaustive. The numbered test cases on

Gradescope are the same as those in the sample autograder, while the

lettered test cases are hidden test cases that will not be disclosed. If your

program passed the former but failed the latter, please double-check if it

can handle all corner cases correctly. Do not try to hack or exploit the

autograder.

Submission

You must submit a .zip archive containing all fi les needed to compile

nyufile in the root of the archive. You can create the archive fi le with the

following command in the Docker container:

$ zip nyufile.zip Makefile *.h *.c

Note that other fi le formats (e.g., rar ) will not be accepted.

 Lab 4: File Recovery

 16/18

You need to upload the .zip archive to Gradescope. If you need to

acknowledge any infl uences per our academic integrity policy, write them

as comments in your source code.

Rubric

The total of this lab is 100 points, mapped to 15% of your fi nal grade of this

course.

Milestone 1: validate usage. (40 points)

Milestone 2: print the fi le system information. (5 points)

Milestone 3: list the root directory. (10 points)

Milestone 4: recover a small fi le. (15 points)

Milestone 5: recover a large contiguously-allocated file. (10 points)

Milestone 6: detect ambiguous fi le recovery requests. (5 points)

Milestone 7a: recover a small fi le with SHA-1 hash. (5 points)

Milestone 7b: recover a large contiguously-allocated file with SHA-1

hash. (5 points)

Milestone 8: recover a non-contiguously allocated file. (5 points)

Tips

Don t procrastinate

This lab requires signifi cant programming effort. Therefore, start as early

as possible! Don t wait until the last week.

Some general hints

Before you start, use xxd to examine the disk image to get an idea of

the FAT32 layout. Keep a backup of the hexdump.

After you create a fi le or delete a fi le, use xxd to compare the hexdump

of the disk image against your backup to see what has changed.

You can also use xxd -r to convert a hexdump back to a binary fi le. You

can use it to hack a disk image. In this way, you can try recovering a fi le

 Lab 4: File Recovery

 17/18

manually before writing a program to do it. You can also create a non?contiguously allocated file artifi cially for testing in this way.

Always umount before using xxd or running your nyufile program.

When updating FAT, remember to update all FATs.

Using mmap() to access the disk image is more convenient than read()

or fread() . You may need to open the disk image with O_RDWR and map

it with PROT_READ | PROT_WRITE and MAP_SHARED in order to update the

underlying fi le. Once you have mapped your disk image, you can cast any

address to the FAT32 data structure type, such as

(DirEntry *)(mapped_address + 0x5000) . You can also cast the FAT to

int[] for easy access.

The milestones have diminishing returns. Easier milestones are worth

more points. Make sure you get them right before trying to tackle the

harder ones.

Thislab has borrowed some ideasfrom Dr. T. Y. Wong.

 Lab 4: File Recovery

MTK平台android recovery模式不删除FAT分区 原理:在android系统的recovery模式下,系统将进入data分区的格式化,而不是mount data分区后进入文件的删除,所以我们需要将系统进入recovery模式下格式化data分区修改成mount data分区,然后进入文件以及目录的删除。而MTK平台正常情况下MTK_SHARED_SDCARD = yes 这种模式下,系统编译后运行时FAT和data分区时合并在一起共享的,所以FAT的物理空间在data分区的范围内。在格式化data分区时会一并将FAT分区给格式化掉。所以需要进行mount后 阅读详情

相关推荐

小米电视E43S救砖实战:TTL刷入Recovery与系统分区修复指南

本文详细介绍了小米电视E43S救砖实战指南,通过TTL刷入Recovery与系统分区修复。从硬件连接到终端配置,逐步指导如何正确刷入recovery.img和boot.img镜像文件,恢复电视正常启动,并提供了常见问题的解决方法。

tech5的博客 1153

FAT12镜像查看工具

为了搞定OS的Lab2实验——实现一个FAT12镜像查看工具,还是耗费了较多的精力的,以此文记录下收获。

qq_66026801的博客 898

移动硬盘格式选择指南:NTFS、exFAT、APFS、FAT32跨系统兼容性与数据安全实战

文件系统是操作系统用于管理存储设备上数据存储、检索和组织的一套规则与方法,它定义了数据如何被写入、读取和索引。其核心原理在于通过元数据(如文件分配表、索引节点)来追踪文件位置与属性,并在磁盘上建立逻辑结构。不同的文件系统在单文件大小限制、日志功能、权限管理和兼容性上存在显著差异,这直接决定了数据在不同平台间迁移的可行性与安全性。从技术价值看,选择合适的文件系统能保障数据完整性、提升存取效率,并避免因格式不兼容导致的读写障碍。在应用场景上,无论是Windows、macOS、Linux多系统协作,还是连接游戏主

weixin_30509393的博客 495

FAT32文件和目录的组织方式

文件在硬盘、SD卡等存储,而里面存储的都是二进制数据,驱动程序是如何从这堆二进制数据中,解析出目录层次、文件列表、文件内容的呢?这就必须要了知道FAT32文件系统在存储介质中的组织方式了。所谓组织方式,就是一种约定或规定,大家都按这套规则来读写就好了。

野生猿-群号1025127672 4470

珍藏多年高效误删除数据恢复工具SoftPerfect File Recovery实战推荐

企业环境中常存在专有文件格式(如.prj.dat等),标准签名库难以覆盖。为此,SoftPerfect提供自定义文件类型注册接口,允许用户添加新的识别规则。操作步骤如下:进入菜单【Tools】→【Options】→【File Types】;点击【Add】按钮新建条目;输入扩展名(如.mydb设置起始签名(如对应ASCII“MYDB”);可选配置结束符、最小尺寸、编码方式等;保存后重启扫描即可生效。

weixin_29069575的博客 1269

VScode中配置 C/C++ 环境,超级详细,问题分析全面,绝对好用

VScode中配置 C/C++ 环境,超级详细,问题分析全面,绝对好用 VScode中配置 C/C++ 环境 你好! 这是你第一次使用 Markdown编辑器 所展示的欢迎页。如果你想学习如何使用Markdown编辑器, 可以仔细阅读这篇文章,了解一下Markdown的基本语法知识。 1. 下载编辑器VScode 1.官网:https://code.visualstudio.com/ 2. 安装VScode(建议附加任务全部勾选; 2. 下载编译器MinGW并解压 官网页面:https://www.mi

m0_46147064的博客 8万+

FAT32格式理解

1 硬盘结构 由上面可知,主引导记录MBR中的分区表有4个分区项目,每个分区项可以放一个主分区,也就是表中的基本分区,或者放一个基本分区。所以系统最多有四个主分区,但是如果我们想要更多的分区的话,我们可以放扩展分区,一个扩展分区可以扩展无限个逻辑分区。上图有三个主分区,一个扩展分区,扩展分区扩展为2个逻辑分区。 扩展分区是如何扩展的呢,其实,每个逻辑分区的头部都有一个字段指向下一个逻辑分区

shuange3316的博客 7510

基于 Quest 摄像头数据开发的原理介绍【Unity Meta Quest MR 开发教程】

比如想在识别到的现实物体上叠加虚拟物体,需要知道这个现实物体在 Unity 的世界坐标下的哪个位置,是带有 x,y,z 三个轴的数据的。而 WebCamTexture 捕捉到的图像只是个 2D 的平面,没有三维世界的深度信息,我们通过物体识别算法识别到的物体坐标只是在这个 2D 平面上的一个屏幕坐标,可以理解为 Quest 拍摄了一张照片,我们识别到这张照片上的某个像素点为需要识别的现实物体的中心。是不是看起来比较复杂?Quest 的相机访问功能是在安卓的。

qq_46044366的博客 2108

windows无法访问指定设备路径或文件_完全免费的文件数据恢复工具:Microsoft Windows File Recovery...

意外删除文件的经历是大多数人都遇到过,但是幸运的是有一种“后悔药”可以吃,因为我们可以使用一些【数据恢复软件】以找回一些已删除的文件。市面上有很多这类型的软件,例如EasyRecovery、DiskGenius、Recuva 等软件。但是,功能强大的专业文件恢复毕竟,软件通常是昂贵的,毕竟“数据是无价的”。最近,微软正式推出了【完全免费的数据恢复工具:Windows File Recovery】。...

weixin_39771987的博客 399

Unity ECS 之 Entitas 的简单介绍,插件下载、导入,和简单使用(一篇文入门搞懂ECS是什么)

Unity ECS 之 Entitas 的简单介绍,插件下载、导入,和简单使用(一篇文入门搞懂ECS是什么) 目录 Unity ECS 之 Entitas 的简单介绍,插件下载、导入,和简单使用(一篇文入门搞懂ECS是什么) 一、简单介绍 二、一些专有项简介 Entity Context Group Collector Matcher System Feature 三、注意实现 四、ECS 的下载 Github 上下载 Unity Asset Store 中下载 U...

仙魁XAN 7780

车载以太网测试技术解析

在智能汽车与HiL测试领域,高效解析与模拟车载网络通信是开发验证的关键。ZD-Converter 2000以媒体/介质转换器、嗅探器、拦截器、仿真器四合一的颠覆性设计,成为工程师应对复杂车载以太网测试的瑞士军刀。它支持双路车载/标准以太网智能转换、实时通信嗅探、硬件级数据拦截及ECU通信模拟,更通过串口命令实现全参数远程配置,赋能自动化测试流程。本文将深度解析其核心功能与实战应用场景。

Triv2025的博客 1143

7个免费的Windows数据恢复工具

有时候,当不小心删掉一些重要文件之后你会非常后悔,那么数据恢复软件就是帮助你重新获得这些删除文件的重要解决方案。如今市场上有很多免费的数据恢复软件可以帮助你恢复已经删除的文件,在这里,小编将为大家介绍7个免费的Windows数据恢复工具,希望能够帮助到大家! Recuva 不小心删掉了重要的文件?电脑死机之后丢失了文件?这些都不重要,Recuva能帮助你从你的Windows电脑、回收站、数码相

zi_wu_xian的专栏 7162

论文阅读:Query-Dependent Video Representation for Moment Retrieval and Highlight Detection

近年来,随着视频理解需求的急剧增加,视频时刻检索和高亮检测(MR/HD)成为人们关注的焦点。MR/HD的主要目标是对给定的文本进行视频时刻定位和内容一致性估计,即显著性得分。尽管最近基于transformer的模型带来了一些进步,但我们发现这些方法并不能完全利用给定查询的信息。例如,在预测时刻及其显著性时,有时会忽略文本查询与视频内容之间的相关性。为了解决这个问题,我们引入了基于查询的DETR (QD-DETR),这是一种为MR/HD量身定制的检测transfomer。

qq_42681787的博客 921

File Recovery和File system

InObjectivesOverviewusage is:means:Your tasks● -i● -lunmounted.

welco5655389的博客 320

RK3568平台开发系列:Android环境下CAN的使用

在RK3568平台上,我们可以利用Android环境中的API来实现CAN的使用。通过以上步骤,我们可以在Android应用中发送和接收CAN数据,并进行相应的处理。当接收到CAN数据时,将触发onMessageReceived回调方法,我们可以在这个方法中对接收到的数据进行处理。在上述代码中,我们指定了CAN的ID为0x123,数据为{0x01, 0x02, 0x03},并设置了标志位和周期。接收CAN数据需要注册一个监听器,并在监听器中处理接收到的数据。发送CAN数据需要指定CAN的ID和数据。

2301_79330513的博客 1914

3D扩散模型的构建与优化:多模态融合在三维物体生成中的作用【附核心代码实例】

随着技术的发展,基于扩散模型的3D内容生成已经成为一个激动人心的领域。通过不断优化扩散模型的结构和算法,结合多模态信息、视角控制和高效网络架构,未来的3D生成技术将不仅能够生成逼真的物体,还能满足虚拟现实、游戏设计、电影制作等行业对高质量、实时生成的需求。

一键难忘的博客 2864

Active File Recovery支持哪些存储设备?

Active File Recovery 兼容多种存储设备,涵盖常见的物理介质和虚拟存储方案。

blwwpyen5834d的博客 270

STM32堆栈溢出问题及解决方法

堆栈是用于存储函数调用和局部变量的内存区域,它是一种先进后出的数据结构。如果函数嵌套层级过深或者局部变量占用的内存空间过大,堆栈的大小可能不足以容纳这些信息,从而导致堆栈溢出。在一些特殊情况下,可以使用堆内存替代堆栈,以避免堆栈溢出问题。在STM32的工程中,可以通过修改链接脚本文件(.ld文件)中的堆栈大小参数来增加堆栈空间。通常,堆栈大小设置为RAM的一小部分,但需要根据具体应用的需求进行调整。堆栈溢出是嵌入式系统开发中常见的问题之一,特别是在使用STM32微控制器时。3.3 使用堆内存替代堆栈。

ZwcCsharp的博客 2597

windows无法访问指定设备路径或文件_误删文件?试试微软免费数据恢复软件「Windows File Recovery」...

相信有些粗心的用户在整理文件资料时会误删重要文件,虽然误删文件可以从回收站里找回来,但是回收站也被你清空了的话,这时候就需要一款数据恢复软件了。目前市面上数据恢复软件选择非常多,有免费和收费,大多数都是大同小异,主要对恢复文件的算法不一样,文件恢复出来的结果也会不一样。今天雷锋哥要给大家推荐微软出品的免费数据恢复软件「Windows File Recovery」目前上架在微软商店里,需要「Wind...

weixin_39610594的博客 470

温度PID控制PLC程序

温度PID稳定控制程序,适用于欧姆龙PLC,对其他PLC也具有很大参考价值

win10 跳过U8环境检测的IE WebControls.rar

win10 安装u8的时候 提示IE WebControls 不通过,这个工具可以欺骗u8的检查。 跳过U8环境检测的IE WebControls。提示导入失败后,重新检测通过。

怎么借助Windows File Recovery恢复文件夹或文件?

本文向你介绍了使用Windows File Recovery恢复文件夹或文件的方法,你可以跟随文中的步骤进行操作。

wenyizhao的博客 2049

Statistics and Machine Learning Toolbox

Statistics and Machine Learning Toolbox(带书签),MATLAB统计学习工具

Windows File Recovery命令不起作用怎么修复?

Windows File Recovery命令不起作用怎么修复?这里有几个可行的解决方法。

wenyizhao的博客 1300

Devexpress16.2.6破解工具

Devexpress16.2.6破解工具Devexpress16.2.6破解工具Devexpress16.2.6破解工具Devexpress16.2.6破解工具

除了U盘,你的硬盘也能救活BIOS:华硕主板Recovery mode隐藏技巧与原理浅析

本文深入探讨了华硕主板BIOS恢复的硬盘方案,揭示了被忽视的底层逻辑与实战指南。通过分析BIOS恢复模式的工作原理,对比硬盘与U盘方案的优劣,提供详细的文件部署和恢复流程,帮助用户在紧急情况下利用内置硬盘高效恢复BIOS。

weixin_30291791的博客 599

conda恢复默认源_误删文件?试试微软免费数据恢复软件「Windows File Recovery」

相信有些粗心的用户在整理文件资料时会误删重要文件,虽然误删文件可以从回收站里找回来,但是回收站也被你清空了的话,这时候就需要一款数据恢复软件了。目前市面上数据恢复软件选择非常多,有免费和收费,大多数都是大同小异,主要对恢复文件的算法不一样,文件恢复出来的结果也会不一样。今天雷锋哥要给大家推荐微软出品的免费数据恢复软件「Windows File Recovery」目前上架在微软商店里,需要「Wind...

weixin_29666489的博客 453

天蚕再变变变。。。。。4320h-acn-V7-FIT变V5-fat-现变V7 fit 全流程

这是第一部曲:从V7 FIT 变回 V5的FAT,也就是所谓的隆级 具体过程如下 System is starting... Press Ctrl+D to access BASIC-BOOTWARE MENU Booting Normal Extend BootWare The Extend BootWare is self-decompressing................................... ......Done! ***************************

zchecb的专栏 2304

Redpill Recovery:5分钟掌握黑群晖终极部署方案

还在为复杂的黑群晖安装过程而烦恼吗?Redpill Recovery(简称RR引导)作为一款革命性的开源引导工具,通过智能化的预安装环境,让普通用户也能在x86/x64设备上快速搭建专业的群晖系统。无论你是技术新手还是资深玩家,本指南都将带你轻松掌握RR引导的核心部署技巧,实现高效的黑群晖部署。 ## SEO关键词优化 **核心关键词**:Redpill Recovery、RR引导、黑群晖、N

gitblog_01163的博客 491

转:5 Must Have File Recovery Tools For Linux Users

By Umar Anjumon August 11, 2011 http://www.smashingapps.com/2011/08/11/5-must-have-file-recovery-tools-for-linux-users.html Creating a backup of your computer is a wise idea. It helps avo...

weixin_30902251的博客 88
上一篇: COMP229 – Web Application
下一篇: Architectural Engineering Design
wx____codinghelp
博客等级 码龄2年 771粉丝 115原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值