Jump to content











Photo

Odd read-only switch behavior


  • Please log in to reply
1 reply to this topic

#1 taa

taa

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 03 March 2013 - 04:57 AM

Firmware 1624, service code 5C4D-857D-2F4A-C827

 

Win 7 Pro 64bit

 

1. Using Windows Explorer, I did a copy-and-paste of config/iso_filename.txt with the intent of creating a copy within the config folder. I got an error because the isostick was read-only, so without removing the isostick I flipped the switch to write-enable it. I was then able to successfully copy-and-paste the file.

 

What happened next is bizarre -- I wanted to rename the file to take out the "Copy" text Windows Explorer inserted, but there was no rename choice in the Windows Explorer context menu. I had to remove/re-insert the isostick before I got the rename option. I can't figure out why I could write to the isostick to make the copy, but then not have a rename option. I could understand it if, even after flipping the read-only switch without removing/re-inserting the isostick, it stil refused to do the copy, but that isn't what happened.

 

2. I don't know if it's related but after I did the above there were another weird thing that happened. I was in the process of installing Lubuntu on a PC and it didn't seem to like the on-board video (at least, that's what I think is the problem). What is strange is that when I rebooted the PC, suddenly the isostick wasn't being found as a CDROM drive. I had to power cycle the PC to get it to be recognized as a CDROM again.



#2 elegantinvention

elegantinvention

    Frequent Member

  • Developer
  • 309 posts
  • Location:South Bend, Indiana, USA
  •  
    United States

Posted 04 March 2013 - 07:33 PM

What happened next is bizarre -- I wanted to rename the file to take out the "Copy" text Windows Explorer inserted, but there was no rename choice in the Windows Explorer context menu. I had to remove/re-insert the isostick before I got the rename option.

I have experienced this as well. It seems to be a Windows Explorer bug, sometimes closing the Explorer window and opening a new one will fix it.

Of course, it's possible isostick is incorrectly reporting the change from Read-only to Read/Write state. I believe what it does is correct per SCSI specs, but I will make a point to observe the behavior of other devices with read-only switches and see if they do anything different.

 

What is strange is that when I rebooted the PC, suddenly the isostick wasn't being found as a CDROM drive. I had to power cycle the PC to get it to be recognized as a CDROM again.

That is indeed strange, and probably is a bug in isostick firmware. I recommend updating to the latest beta firmware, r1677. If the problem happens again after updating to r1677, please let me know and I will see what we can do to get it fixed.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users