Sorry, I have found this advice in email list history. Thank you for
understanding.
On Friday, April 17, 2020, 07:17:14 PM GMT+3, Flaviu2
wrote:
I do not understand why you partially use the ntfs-3g startup
code, without using the routines which ntfs-3g uses for
accessing the partitio
I do not understand why you partially use the ntfs-3g startup
code, without using the routines which ntfs-3g uses for
accessing the partitions when running on Windows.
You said about ntfs_device_win32_open from win32_io.c file ?On Thursday,
April 16, 2020, 08:28:30 PM GMT+3, Flaviu2 via ntfs
I do not understand why you partially use the ntfs-3g startup
code, without using the routines which ntfs-3g uses for
accessing the partitions when running on Windows.
Seem that is only chance ... I'll try this ... can you give some
advices/functions as you better this library ? Kindly thank you
Flaviu2 wrote:
Is there any way to know for sure if I accessed alright the NTFS drive ?
The purpose of the function ntfs_boot_sector_is_ntfs() is to
be reasonably confident about it. If the function fails, you
know you are NOT processing an ntfs partition.
I do not understand why you partially
Is there any way to know for sure if I accessed alright the NTFS drive ?
(Which is in fact an USB drive)
To eliminate this problem once ...
On Friday, April 10, 2020, 07:00:05 PM GMT+3, Flaviu2 via ntfs-3g-devel
wrote:
I guess I succeeded into reading the NTFS drive with this approach
I guess I succeeded into reading the NTFS drive with this approach:
"?\\E:"
ran as admin mode.
But I guess the issue is a little bit earlier. Let see the code, in device.c
file
ntfs_volume* ntfs_volume_startup(struct ntfs_device *dev, ntfs_mount_flags
flags){... // Now read the bootsec
Flaviu2 via ntfs-3g-devel wrote:
"You are unlikely to be able to access the system partition
C: in read-write exclusive mode, this obviously conflicts
with system access.
Also low-level opening of a partition is done with the
prefix \??\ which you might try."
My code looks like that:
/hd_h = _
"You are unlikely to be able to access the system partitionC: in read-write
exclusive mode, this obviously conflictswith system access.
Also low-level opening of a partition is done with theprefix \??\ which you
might try."
My code looks like that:
hd_h = _open(".\\C:", mode);
I have tried
Flaviu2 wrote:
This time I've tested my C: drive, which is also a NTFS drive, of
course, with exactly the same result. And I read what I have feed in
"device" argument:
"What do you feed into the "device" argument ?"
\\.\C:
You are unlikely to be able to access the system partition
C: i
This time I've tested my C: drive, which is also a NTFS drive, of course,
with exactly the same result. And I read what I have feed in "device" argument:
"What do you feed into the "device" argument ?"
\\.\C:
I haven't used win32_io.c file ... would help me to solve my issue ? Since the
act
Flaviu2 wrote:
Kindly thank you for your time.
I have tested my *local HDD*, which is also NTFS, I attached the
hexdump also (hexdumpLocalHDD.txt), and I noticed that I got the
following message from Frhed app, and of course, my *HDD* NTFS is
working well.
Inline image
I have also checked
Mingye Wang wrote:
On Thu, Mar 5, 2020 at 8:04 PM Flaviu2 via ntfs-3g-devel
wrote:
Hello.
I attach the hexdump file at this email (is a small file, hexdump.txt)
Do you see the "error loading operating system" part of the dump? I
believe you are reading the disk, not the NTFS partition/volume.
On Thu, Mar 5, 2020 at 8:04 PM Flaviu2 via ntfs-3g-devel
wrote:
>
> Hello.
>
> I attach the hexdump file at this email (is a small file, hexdump.txt)
Do you see the "error loading operating system" part of the dump? I
believe you are reading the disk, not the NTFS partition/volume.
Regards,
Ming
Hello.
I attach the hexdump file at this email (is a small file, hexdump.txt)
I loaded the NTFS library in a test VC++/MFC project and I used to read a NTFS
drive. I can list the function that has been called until the failure:
// 1.volume.cntfs_volume* ntfs_device_mount(struct ntfs_device *dev,
Flaviu2 via ntfs-3g-devel wrote:
Hello Pierre.
I am afraid I cannot run "blkid path-to-partition" command because I
don't have a Linux OS, just Win10.
Then, can you at least post an hexadecimal dump of the beginning
of the boot sector you read in the buffer pointed at by "b"
(64 bytes should
Hello Pierre.
I am afraid I cannot run "blkid path-to-partition" command because I don't have
a Linux OS, just Win10.
Yes, I am trying to read a USB stick formatted as NTFS. That is for sure.
I am just suspecting that library doesn't read Win10 ntfs drives due to this
issue (from my post) and b
Flaviu2 via ntfs-3g-devel wrote:
Hello. I have loaded NTFS-3G from here:
https://github.com/vitalif/ntfs-3g into a VS2017 project, wanting to
read NTFS USB stick drive. And when I debugging reading process, I saw
that is not reading USB drive due to:
*// bootsect.c*
BOOL ntfs_boot_sector_is_
Hello. I have loaded NTFS-3G from here: https://github.com/vitalif/ntfs-3g into
a VS2017 project, wanting to read NTFS USB stick drive. And when I debugging
reading process, I saw that is not reading USB drive due to:
// bootsect.c
BOOL ntfs_boot_sector_is_ntfs(NTFS_BOOT_SECTOR* b){ u32 i; BOOL r
18 matches
Mail list logo
