| Author | Message | ||
     Chris Randle (Narny) |
Using 11.5 SR-10 I have a script which I start with a physical disk already open in WinHex. I copy a block of the disk to the clipboard. I then Open an existing file and try to Goto a particular place in that file. The script actions the Goto on the Disk window, not the file I've just opened. I tried NextObj, thinking that WinHex opened the file but didn't make it the active Window, but it still operated on the disk window. The workaround is two NextObj's in a row but I'm not sure that the script should be behaving like this. Example script: // Disk (physical medium) already open // It is the only window open block1 CurrentPos move 0x3F block2 CurrentPos copy open "J:\Recovery3\HeaderTest.txt" goto 0x123 // This moves the disk window ptr nextobj nextobj goto 0x123 // This moves the file window ptr | ||
| Stefan Fleischmann (Admin) |
Sorry, I cannot reproduce this error. Feel free to send me a screenshot, so I can recreate the situation as close as possible. | ||
| Chris Randle (Narny) |
Sorry, my fault Stefan. I simplified the example script but didn't test it to make sure it still triggered the problem. I've tried again with the script below and commented which lines need to stay in order to reproduce the problem. I made File1.txt containing The quick brown fox jumps over a lazy dog and File2.txt containing Now is the time for all good men to come to the aid of the party Both files end 0x0D0A when viewed in WinHex. Open File1.txt in WinHex manually (but not File2) and then execute the following script. // Removing the next line makes the script work OK goto 2 // Removing the next 2 lines makes the script work OK assign FileCount 0 inc FileCount // Removing the next 5 lines makes the script work OK block1 CurrentPos move 10 block2 CurrentPos copy move -5 open "C:\File2.txt" // Removing the next line makes the script work OK assign EndPtr 16 // The following goto is actioned on File1.txt not File2.txt goto 16 | ||
| Stefan Fleischmann (Admin) |
Thank you, and sorry for the trouble. Will be fixed with the next WinHex version. |