Products > Test Equipment

Agilent E8357A

<< < (24/28) > >>

joeqsmith:
Check the EEPROMTOOL.EXE.   Remember mine crashed when I tried to run BACKUP.EXE.   When I went to minimize the PNA software, I saw that dialog.   Having tried both, it may be from the other program.   If you don't see it there,  I'll try and replicate the steps I took.   It's very possible that EEBACKUP.EXE is hardcoded to store the data to the D:\calfiles which may explain why it crashed on my PNA as I never setup the second partition.   You would think that it would post something more useful, like "D:\calfiles not found" "Would you like to backup the data to another location"...   

Forzaman:
I attached a document that describes the procedure to use multiple drives on a PNA, or a single drive on multiple PNAs. It mentions that on older PNAs, the EEPROM data is backed-up to D:\calfiles.

joeqsmith:
Currently my PNA has a single SSD with only one partition setup.  While the original HDD that was supplied with my PNA has a second partition which would have been identified as D:\,  I have no use for it and did not set it up.   The original eebudata.dat on my PNA was stored under D:\calfiles.   When backing up the data, I had it save to  E:\MXCAL which again, is the my desktop PC.  I thought I had made all of that clear before but I am guessing you feel it somehow matters where they are stored?   

One reason I wanted the PNA was for the Ethernet connection.  With it being Windows based, it's a breeze to interface with it.  Not just moving files but also for controlling it. 

I have not had the PNA on today and didn't try the other program to see if this was how I was able to select the target location. 

Forzaman:
I just provided the document to confirm your suspicion that the older PNAs default to the D:drive for EEPROM data backup. Other than the EEPROM backup, it appears that it doesn't matter where files are stored. No need to try and reproduce the menu that allows the user to specify the location... again, I just mentioned that I couldn't get it for your information since you posted your observations. I'm happy with it defaulting to D: drive.  BTW, I bought a SSD (Transcend 64GB) to see if it would speedup the OS, but for some reason my duplicator doesn't work with the SSD as the target. May have to use cloning S/W instead.

joeqsmith:
I did try to replicate my findings but ran into some really strange problem.  Maybe you can reproduce it.

I tried to run the EEBACKUP.EXE tool again and get the same crash.  I then ran the EEPROMTOOL.EXE and could select the target location and file name as before.   So, this is the tool I used to create the EEPROM.DAT file I uploaded.   

Next I ran a diff between the original EEBUDAT.DAT file that came with the PNA.  These two files are not the same.  Even their sizes differ.

Next I setup a FAT32 partition and set it to to drive D.  I did not install any files or create any directory structures on it.  I then ran the EEBACKUP.EXE.  This time no obscure error and it counts as it reads the data.  It then creates a new directory D:\Calfiles with EEBUDAT.BAK and EEBUDAT.DAT.   Running a diff on these to files, they match.   

Next I ran a diff on them against the original EEBUDAT.DAT file that came with the PNA.  These do NOT match!!!   

On a hunch, I reran the EEBACKUP.EXE program and created two new files.   Running a diff on these to files, they again match.   I then ran a diff between them and the previous ones I created.  These do NOT match!!!  |O

I'm glad I didn't try a restore.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod