I've been looking at the cal data related stuff in firmware a little bit and started a thread about it over here:
https://www.eevblog.com/forum/testgear/lecroy-x-stream-calibration-data-and-storage/Looking back over this thread I would like to correct some old posts and explain "weird behavior" for the benefit of anyone swapping out their hard drive.
I had 20G drive C:, and 20G userdata (which contains the calibration data). The userdata partition was contained in a logical partition. Just moving the partition content to a primary partition with dd on linux made the software complain that the calibration data was moved.
Partition type doesn't matter -- it's looking for a drive letter D: with a volume name of USERDATA. You probably just didn't set the volume label when setting up the partition from Linux.
Yes, got exactly the same message. I've now recreated the logical partition, and moved that to the end of the disk. So the position on the disk in terms of sectors doesn't matter, but the partition numbering does.
See above. It can even be a separate disk as long as the letter is D: and the volume name is USERDATA.
Firmware calls GetVolumeInformationW with a root path name of "D:\" and checks the returned volume name for a match to USERDATA.
I'm not sure whether it has to be on a logical partition. I would rather think that they store the partition location during calibration and so it can't be moved later.
That is not the case. The possible locations are hard-coded. First it will look for a D: drive with volume name USERDATA and if that fails then it will fall back to C:\LeCroy\XStream for the Maui root path and C:\LeCroy\XStream\Calibration for the Maui calibration path.
Well, it's rather interesting... I changed my calibration partition to be the second partition. Tried as both physical partition and as an extended partition. Formatted as either FAT32 or NTFS. Still getting the same error. Obviously, it's always mounted on drive D:\ and has "USERDATA" as a volume name. I have verified that XStream is reading and writing the config files to this filesystem. In fact, I can back up and restore the calibration data back using XStream "Critical files backup" procedure which is the official procedure to restore calibration data when changing the hard drive. I'm starting to suspect that it's going to be something else... what am I missing?
The "unidentified structures" messages at bootup means that some data points in the BTD files were not filled out. It appears these are not critical errors but everybody notices them for the first time when troubleshooting the nasty popup message and believes they are related when they are not.
If you don't have a Calibration folder at the right location before firmware starts then you will get the popup message. Once you answer either yes or no, it will set a registry key (HKCU\SOFTWARE\LeCroy\Maui\ShowCalibrationDataError) that will either always show the popup or never show the popup. So it will keep coming back even after you restore the cal data! To make it go away, just delete the registry key (instead of setting it to 1 or 0).
Also, my calibration issue is somehow resolved after installing XStream under Windows 7. I'm using the same calibration partition mounted as "D:\" drive in both Win XP and Win 7, but after installing XStream software under Win 7, I'm not seeing this error any more. If I re-boot back into Win XP, the error comes back. Weird...
That's because the registry key exists in the XP registry but not in the Win7 registry -- you already had the D: drive set up when you installed Win7 so you never got the message box and never added the registry key in Win7.
Do you mean I simply need to create a C: and D: partition? Or is there something more specific I need to do?
Your options are to create a D: partition named USERDATA, install a second D: drive and name the volume USERDATA, or you can just ignore that step and run on a single C: drive.
I think to avoid the prompt in the first place you need to create the D:\Calibration folder or the C:\LeCroy\XStream\Calibration folder before launching firmware, but I wouldn't worry about it. Just decide if you want a D: drive or not for your calibration and save files, set it up if you want it, install firmware, restore your cal data, and then delete the registry key that makes the popup always show.
I actually did some thorough looking at the registry. I looked through everything I could find with "LeCroy" and there was nothing about cal data, location of it, or even that the message should appear/not appear. Very little in the registry from what I could find.
You were looking under HKEY_LOCAL_MACHINE but the setting you were looking for is under HKEY_CURRENT_USER
I WONDER. My scope is a WaveRunner 6100. Perhaps your is different and therefore produces different files?
From what I can see in the firmware, no. I believe all the XStream scopes are using the same calibration methodology with the same named files and data structures inside. It's a very small amount of data stored at a single operating temperature so corrections for all other operating points would have to be extrapolated. My guess is that the extrapolations to other operating points are stored in the cache files for faster lookup the next time and the caches are not part of the critical files backup.
Interestingly, today I decided to log in using LeCroyUser and to my amazment, when I run Start DSO, I do not get the error message!
That is because the registry key that FORCES the message to appear on every launch of firmware is stored under HKEY_CURRENT_USER. Log in as a new user and the key is gone! As long as the calibration folder is in the right place then the message box won't appear and the registry key will not be added.
I think that the system remembers that at some point in the downloading process, there were no calibration data and suggested that you contact LeCroy service for this.
That's right, once it gets tripped it doesn't go away unless you tell it to never come back, but then it will never ever be displayed even if your cal data does go missing, which is why I recommend deleting the key altogether.