Exactly, that's what I suggest, replace it, put size in properties sheet. With LBA values in one view an experienced tech can easily tell if partition tables make sense. It's always where my eyes go first, offset + LBA size should take you to next partition without having to convert GB to LBA. That's what I consider usability, nothing to do with cosmetic. Do what you want with it, it's a request.1) This is "nonsense" if you replace MB/GB/TB with LBA
UFS Explorer Feature Requests & Bug Reports
-
- Official Product Rep
- Posts: 172
- Joined: Tue Feb 07, 2017 2:18 pm
- Location: Netherlands
- Contact:
Re: UFS Explorer Feature Requests & Bug Reports
http://www.disktuna.com - video & photo repair & recovery service
Re: UFS Explorer Feature Requests & Bug Reports
Can you fix html reports on Mac? Trying to make html report causes UFS to crash/quit (at least on 10.15).
Re: UFS Explorer Feature Requests & Bug Reports
- This function doesn't exist in DRE so I assume it can't be set via specific network call (DRE asks to use "DDI intrface" directly). In this state UFS Explorer can access "DDI terminal", so you can do this via UFS Explorer by connecting terminal and setting Project ID.
If one day DeepSpar will implement this function as direct call over network, we will be able to implement it in UFS Explorer.
Last edited by sdl on Mon Jan 04, 2021 9:42 am, edited 1 time in total.
Re: UFS Explorer Feature Requests & Bug Reports
This sounds like problem of saving HTML reports from HFS+ file system that was fixed in version 8.10 or 8.9 (problem reason - CRT API specifics, no NULL-check where it is checked under other OSes).
In your case, is this issue reproducible with the latest software version?
Re: UFS Explorer Feature Requests & Bug Reports
Thank you, confirmed fixed!
sdl wrote: ↑Mon Jan 04, 2021 9:39 amThis sounds like problem of saving HTML reports from HFS+ file system that was fixed in version 8.10 or 8.9 (problem reason - CRT API specifics, no NULL-check where it is checked under other OSes).
In your case, is this issue reproducible with the latest software version?
Re: UFS Explorer Feature Requests & Bug Reports
Cool. You guys rock!
- CrazyTeeka
- Lurker
- Posts: 155
- Joined: Sat Jul 20, 2019 7:12 pm
- Location: UK
Re: UFS Explorer Feature Requests & Bug Reports
When I use IntelliRAW Rules Editor to make some custom rules. I would like you to add support for 5 bytes for "Size defined at file start as". I think 4 bytes is too limited when we are dealing with video files over 4GB. Because only 4 bytes of the 5 bytes are being read UFS Explorer thinks its a 2.30GB file. It's not seeing the 5th byte at the start which is important.
- Attachments
-
- Web-M.zip
- (257 Bytes) Downloaded 1190 times
Re: UFS Explorer Feature Requests & Bug Reports
Hello,
There is selection of field size. Typically, when field max value exceeds 32bit, there is used 64bit field (e.g. QTFF format uses 64bit for 32bit overflow). If 64bit fields looks reasonable, you may simply select 64bit (little- or big-endian) for field type.
There is selection of field size. Typically, when field max value exceeds 32bit, there is used 64bit field (e.g. QTFF format uses 64bit for 32bit overflow). If 64bit fields looks reasonable, you may simply select 64bit (little- or big-endian) for field type.
- CrazyTeeka
- Lurker
- Posts: 155
- Joined: Sat Jul 20, 2019 7:12 pm
- Location: UK
Re: UFS Explorer Feature Requests & Bug Reports
I've cracked it. By pointing the rule that reads the filesize to start one byte back and reading 4 bytes from that point, then multiplying (x) it by 256 and adding (+) 300, I've had better success. I end up with the full 11GB test webm video file padded with a few 00's on the end. It works fine for smaller sizes of webm video files as well. Pretty much a tested and working custom rule.
- Attachments
-
- Web-M.zip
- Version 2
- (256 Bytes) Downloaded 1240 times