Burningman appears to generate incorrect 09 C/R keys
I recently purchased two CVS camcorders (Monroe, LA) that can't be unlocked with the 09 C/R key generated by burningman.exe. I've tried both the command line and GUI versions of burningman, and both programs generate the same keys. Not sure if I'm doing something wrong, if the algorithm used in burningman doesn't cover all possible keys, or if PD has changed the unlocking method. Specific details are: Camera #1 Model 220 Nerve pinch information: FW-VERSION: 33.21 CAMERA ID: GD3061204575 PCB VER: B1 Burningman C/R key: S MonroeCVS1 C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Camera #2 Model 230 Nerve pinch information: FW-VERSION: 53.14 Realm ID = 20 GFZ064400091 PCB VER: DC-6910 A4 Burningman C/R key: S MonroeCVS2 C 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 C 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 C 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 C 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 R 3c7e53d6b2e5cadbfe297f9d4f90d938319beab15efdbe187e4044a2e2740378 R 6ae637ec817444795dd6d40fc6664a1cdaff79407da0aa11595f19850e20a4cc R 0485aa90fed110b8caa1b4e777676f3f25f373e576d14cc909b9506b1afe590a R 2bc051908f5de0dc6344a1c1cfa1d5d3f963f034b555d5a02252bc99502f19aa I've put both of these keys in saturnkeys.txt, which is shown here: S MonroeCVS1 C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 S MonroeCVS2 C 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 C 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 C 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 C 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 R 3c7e53d6b2e5cadbfe297f9d4f90d938319beab15efdbe187e4044a2e2740378 R 6ae637ec817444795dd6d40fc6664a1cdaff79407da0aa11595f19850e20a4cc R 0485aa90fed110b8caa1b4e777676f3f25f373e576d14cc909b9506b1afe590a R 2bc051908f5de0dc6344a1c1cfa1d5d3f963f034b555d5a02252bc99502f19aa Using Ops 0.23, I obtain the following information about trying to unlock each camera: Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. External key file, saturnkeys.txt was found and will be loaded Challenge and response keys retrieved from camcorder: S YourNameHere C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 R d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 R e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 R b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd Camera revision retrieved from camcorder: 33.21 The challenge key was the same as response. Moving on to try known keys... Checking if the Reset key matches the challenge Checking if the MonroeCVS1 key matches the challenge failed to unlock camcorder Failed to unlock camcorder with what appeared to be a known key! Checking if the MonroeCVS2 key matches the challenge Last ditch attempt. challenge=response, but trying a regular unlock anyway. failed to unlock camcorder Failed to unlock camcorder with key retrieved from memory! Sorry, your camcorder can not be unlocked with any known method. Camcorder USB device closed. Found the camcorder: Pure Digital Inc. Saturn , VID:167B PID:0101 Found camcorder. Connected to camcorder. External key file, saturnkeys.txt was found and will be loaded Challenge and response keys retrieved from camcorder: S YourNameHere C 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 C 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 C 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 C 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 R 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 R 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 R 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 R 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 Camera revision retrieved from camcorder: 53.14 The challenge key was the same as response. Moving on to try known keys... Checking if the Reset key matches the challenge Checking if the MonroeCVS1 key matches the challenge Checking if the MonroeCVS2 key matches the challenge failed to unlock camcorder Failed to unlock camcorder with what appeared to be a known key! Last ditch attempt. challenge=response, but trying a regular unlock anyway. failed to unlock camcorder Failed to unlock camcorder with key retrieved from memory! Sorry, your camcorder can not be unlocked with any known method. Camcorder USB device closed. So have I done something stupid with my procedure, or are there some 09 C/Rs that burningman can't unlock? Thanks in advance.

I'am not sure why but I get a different result from "burningman" yours: S MonroeCVS1 C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 mine: S MonroeCVS1 C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R ea207889be4b8719ccbbcac686b943df5ee5e19323b6d824f0fc9343dad48b55 R 0ad056a20a3f00ad7ad263412636747287483a4664f59c97fdf14c789485080b R d5011958e1835be1ca36b652fd85349f69c09127a02322cf4cfb717a505666cf R 13ec7b00dcef60b5bcbf00ba715c55b9b40a79dbbe479f6791afba92180de588 hope this helps

Wow ... that key you generated does work. Thanks for that one. Which version of burningman are you using? I used the one available from the link on the HowTo discussion thread (GuyFawkes.zip), which has a file length of 34304 bytes and a modification date of Nov 05, 2007, 7:55:46 AM. And the burn.exe file with the burningmangui.zip is of the same length, but with a modification date of Nov 05, 2007, 4:33:12 PM. I tried again this morning, but neither of those versions generated your key. Or is there something else I need to do other than setting the PC date to November 5th?

I tried running burningman on a different PC which had never executed the code before, and discovered something interesting. I get a different result the first time that I run the program on a particular computer. Burningman generated a key different than what you got, and different from what I got ... the first time. After that, it generates the same faulty keys. And all keys generated for me don't unlock the camcorders. Thinking that this was odd, I decided to do a more controlled experiment. I have a Win98 virtual machine, so I copied the Win98 VM drive to a different directory so that I'd always start with a system that never had burningman executed upon it. The results were consistent for both cameras -- I get a different key the first time I run burningman after unzipping the file, but after the first time the keys are consistent with what I posted earlier. And if I re-start the VM with a "virgin" Win98 drive, the pattern repeats. For example, here are two such runs: Experiment #1 S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 2665a58581f9c583944f6105965c855ffaf5949061d099acd4ee2869b9a3e5b5 R a4d941d4a2df57404bf7b6b673aff20e3e44bf6431436340b79f0d4511be327f R 38676f13a8257b6f8daada24b34defbda9ace20ab1b437c7cb44ff7f2826cab7 R 4f58db03390321c251a5cdfdd5563804534cfff1c5227f205f2747bea6945a0e Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . I then erased that VM drive, copied the virgin drive, and ran again with the following results: Experiment #2 S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 2665a58581f9c583944f6105965c855ffaf5949061d099acd4ee2869b9a3e5b5 R a4d941d4a2df57404bf7b6b673aff20e3e44bf6431436340b79f0d4511be327f R 38676f13a8257b6f8daada24b34defbda9ace20ab1b437c7cb44ff7f2826cab7 R 4f58db03390321c251a5cdfdd5563804534cfff1c5227f205f2747bea6945a0e Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . And it doesn't matter which C/R I start with -- I get a different pattern only on the first run of the program, but NOT with the first time that a C/R pair is found. Here I started with one C/R, then the other, then went back to the first: Starting With Camera #1 S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 2665a58581f9c583944f6105965c855ffaf5949061d099acd4ee2869b9a3e5b5 R a4d941d4a2df57404bf7b6b673aff20e3e44bf6431436340b79f0d4511be327f R 38676f13a8257b6f8daada24b34defbda9ace20ab1b437c7cb44ff7f2826cab7 R 4f58db03390321c251a5cdfdd5563804534cfff1c5227f205f2747bea6945a0e Press any key to continue . . . S Guy Fawkes. Nov 5th. C 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 C 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 C 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 C 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 R 3c7e53d6b2e5cadbfe297f9d4f90d938319beab15efdbe187e4044a2e2740378 R 6ae637ec817444795dd6d40fc6664a1cdaff79407da0aa11595f19850e20a4cc R 0485aa90fed110b8caa1b4e777676f3f25f373e576d14cc909b9506b1afe590a R 2bc051908f5de0dc6344a1c1cfa1d5d3f963f034b555d5a02252bc99502f19aa Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . And if I restart the whole VM with the other C/R first, I get the following: Starting With Camera #2 S Guy Fawkes. Nov 5th. C 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 C 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 C 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 C 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 R e1f44a2e52733d87125c5227ad8abff195754222cfc7fb380421a51a3226ab1d R dcc49ab9a48b3875aaf550faf27d2f62e41d67878d8e9c34e9534e6ee6fe766a R 14fdec0cbd6a92115ce11ac6313e04e9438f3bcbb9628f58e5b73b52db29c9ee R 6393182435d6c2846b14e7d048df4a77c1dba03d5dc70d064734fc9e95c928fe Press any key to continue . . . S Guy Fawkes. Nov 5th. C 094b1c970fdb0a35406c3369d4627864c71dcc1bcad98a4b39d20cba4dac79c1 C 9313de079c9f818ff6fa72f55c4462f42ab6b82c1486e222160be989ae2249c0 C 4ad0ff9bfc29e36675703827317f8224ef6997a5645ff9fb30d063c111d4a262 C 57cba6dc9841d9c3a416b088bbdb7ffbfe7e910f242a78dd6e69a2ecdd8c2db0 R 3c7e53d6b2e5cadbfe297f9d4f90d938319beab15efdbe187e4044a2e2740378 R 6ae637ec817444795dd6d40fc6664a1cdaff79407da0aa11595f19850e20a4cc R 0485aa90fed110b8caa1b4e777676f3f25f373e576d14cc909b9506b1afe590a R 2bc051908f5de0dc6344a1c1cfa1d5d3f963f034b555d5a02252bc99502f19aa Press any key to continue . . . S Guy Fawkes. Nov 5th. C 097c0570cec9c76b511c74b2d8b65928444189675eb42fbcc976227235c6ba54 C d45ae36d12466f128120b1231262478d8b0f3713359a3e4fd50364f3de43d455 C e5eaeb2b55078f926448c2564662766da0b3a3c43f26983f0a588ffb35f983d6 C b874463100d2cef4e4dbcfd3da7f90d06b75f701e422e5944fbcca10a1af70dd R 0b52853833ad7a486053df1c16d1d5fa199fb6dfc4880e0f0a0871d6185925b2 R 53fd3d447c4bb0283b2fdb32784dae1af475b8b4ef36bcb071df580abb05bd0c R 4e5e877a1235278cfbdcd44d6b32a81dba8c154837912b9c45caf29bb8593a02 R 427d8aaf7a56a7b156263d0d7f2b5ba35c944cb16c9e73205b71f2eacfc89114 Press any key to continue . . . I'm at a loss to explain this behavior, and am surprised that it generates two different faulty C/R keys for me. :?

my guess would be a dependency on microsoft's crypto library, but it's not working "as expected" on an older version of the crypto dll. either that, or some calculation or permutation within the code is mishandled by the win9x api. anyone confirm? my running in wine doesn't reveal anything, nor do i expect it to. it's possible that it's relying on some older memory table or hash, something along those lines. out of curiosity, is your windows 98 vm first or section edition <4.10.1998 or 4.10.2222>, and is the vm installation fully updated via windows update?

I guess I should have been more clear in the previous posting -- I first observed this behavior on machines with Windows 2000 (updated to the most recent service packs as of yesterday). I don't have a Windows 2000 VM, which is why I used the Windows 98 VM for "controlled" -*test*-('")ing. From what I can tell, the behavior under Windows 2000 and Windows 98 was identical. In fact, the keys generated are identical. The version of Windows 98 is the first edition, and fully updated to the last service packs for that edition. When I have time, I'll create a Windows 2000 VM and see what happens.

what processor are you running, and is the vm's software running on an emulated CPU, or are the instructions executed natively on the host CPU? also, is your system overclocked or something other than intel or amd?

Let's see ... the Windows 2000 machines were an Intel Pentium 4, a Slot A AMD Athlon, and a Socket A AMD Athlon XP 2200+. None of the machines were overclocked. The VM is Microsoft's VirtualPC 2004, which I believe executes the instructions natively. The VM is running on the AMD Athlon XP 2200+. I doubt that the problem is with the virtual machine, since the same behavior is seen with the non-VM Windows 2000 machines. But one never knows.

slingbits, is your copy of burningman hex edited to run on dates other than the 5th, or are you setting the date?

the date edited tag in the file in GuyFawkes.zip is probably different because that was the date that it was zipped. if you check the other files in that folder, do they give the same time? i KNOW that nothings wrong with that version, i added it to the zip folder myself, and have used it from that download several times.

The version included with the GUI isn't hexed to work on any date, the GUI app changes the system date when it runs burningman.

md5 hash, anyone? I've run MD5Summer on the two versions of burningman.exe I've found on the web (one by itself, one zip'd in GuyFawkes) and the burn.exe from burningmangui. All MD5s are the same, so they are the same programs: # MD5 checksums generated by MD5summer (http://www.md5summer.org) # Generated 1/12/08 9:01:31 AM 9995112343f47c20445e41cbdac97044 *BurningMan.exe # MD5 checksums generated by MD5summer (http://www.md5summer.org) # Generated 1/12/08 9:01:58 AM 9995112343f47c20445e41cbdac97044 *BurningMan.exe # MD5 checksums generated by MD5summer (http://www.md5summer.org) # Generated 1/12/08 9:01:45 AM 9995112343f47c20445e41cbdac97044 *burn.exe