I'd like to see a firmware update thread or a mailing list for updates with a detailed change log. I didn't see anything already dedicated to this purpose.
Scott
Firmware Update Thread
Started by
scott3091
, Aug 31 2012 12:54 PM
9 replies to this topic
#2
elegantinvention
-
- Developer
-
- 310 posts
Frequent Member
- Location:South Bend, Indiana, USA
-
United States
Posted 04 September 2012 - 03:12 PM
Note if you hover over the firmware in the updater software (no isostick required!) it will show detailed changelog.
Nevertheless, I'll start posting here
Nevertheless, I'll start posting here
#3
elegantinvention
-
- Developer
-
- 310 posts
Frequent Member
- Location:South Bend, Indiana, USA
-
United States
Posted 04 September 2012 - 03:21 PM
Publishing r1612 (BETA): Proposed fix for misc. crashes.
Should fix crashes during reads and writes, such as in http://reboot.pro/17378/ and http://reboot.pro/17370/
Note that this revision disables auto-reloading of iso_filename.txt for MacOS X and Linux users. This is because osx/*nix do not clear the volume dirty bit when they're done writing, so the isostick cannot be certain the volume is clean. The code used to work around this was likely the cause of this bug.
I'm working on new code to reload the config file without an unmount/remount cycle that won't crash the device.
Should fix crashes during reads and writes, such as in http://reboot.pro/17378/ and http://reboot.pro/17370/
Note that this revision disables auto-reloading of iso_filename.txt for MacOS X and Linux users. This is because osx/*nix do not clear the volume dirty bit when they're done writing, so the isostick cannot be certain the volume is clean. The code used to work around this was likely the cause of this bug.
I'm working on new code to reload the config file without an unmount/remount cycle that won't crash the device.
#4
elegantinvention
-
- Developer
-
- 310 posts
Frequent Member
- Location:South Bend, Indiana, USA
-
United States
Posted 07 September 2012 - 01:12 AM
Taking r1612 out of beta after independent confirmation that it fixes the reported crashes.
#5
themoufty
-
- Members
- 2 posts
-
Canada
Posted 07 September 2012 - 05:21 AM
Taking r1612 out of beta after independent confirmation that it fixes the reported crashes.
It appears this update may require isosel.bin to be tweaked. When booting from the stick, isosel starts, but I am getting an error:
"isostick was not detected - picking an image may not work"
When I select an image, the machine reboots back in to isosel regardless of the choice I have made (assuming I pick to boot from the isostick cd reader)
Anything you would like me to check?
#7
themoufty
-
- Members
- 2 posts
-
Canada
Posted 08 September 2012 - 06:32 PM
Yes, it worked before. Both on an asus motherboard and a Dell Latitude E6100.
Similar to what you suggested in another thread (the pSeries thread?) I have renamed isosel.bin to try and force the isostick firmware to present the selected iso to the machine's BIOS, but it does not work. Switching the ISO using iso_filename.txt appears to work just fine.
Similar to what you suggested in another thread (the pSeries thread?) I have renamed isosel.bin to try and force the isostick firmware to present the selected iso to the machine's BIOS, but it does not work. Switching the ISO using iso_filename.txt appears to work just fine.
#8
elegantinvention
-
- Developer
-
- 310 posts
Frequent Member
- Location:South Bend, Indiana, USA
-
United States
Posted 11 September 2012 - 10:20 PM
@themoufty,
I've tested this out and can't seem to reproduce it, I'll see about building some firmware to keep a log of what happened so I can get to the bottom of it.
Until then, can you explain what happens when you rename isosel.bin?
Thanks.
I've tested this out and can't seem to reproduce it, I'll see about building some firmware to keep a log of what happened so I can get to the bottom of it.
Until then, can you explain what happens when you rename isosel.bin?
Thanks.
#9
elegantinvention
-
- Developer
-
- 310 posts
Frequent Member
- Location:South Bend, Indiana, USA
-
United States
Posted 11 September 2012 - 10:34 PM
Publishing r1616 (BETA): Allows use of forward or backslashes in iso_filename.txt
When specifying filenames in iso_filename.txt you may now use forward or backslashes, for example both "SpinRite.iso" and "/SpinRite.iso" are valid. You may also use a combination of them if you're so inclined, as in: "/ab/cd/blah.iso".
FAT32 filenames do not allow either slash, so this should not pose problems with filenames.
When specifying filenames in iso_filename.txt you may now use forward or backslashes, for example both "SpinRite.iso" and "/SpinRite.iso" are valid. You may also use a combination of them if you're so inclined, as in: "/ab/cd/blah.iso".
FAT32 filenames do not allow either slash, so this should not pose problems with filenames.
#10
elegantinvention
-
- Developer
-
- 310 posts
Frequent Member
- Location:South Bend, Indiana, USA
-
United States
Posted 11 September 2012 - 10:36 PM
Also, I'm going to setup a proper RSS feed and announcement list for firmware updates in the future, at which time I'll retire this thread. If anyone has objections, please speak up
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
