1) Configureable device identifiers. IE, Elegant ISOStick CDRom. This way we could change it to more closely emulate a "regular" cd-rom. Some software use this identifier, and it'd be nice to change it to what the software is expecting.

2) When updating a new firmware, I don't know what firmware is currently loaded without having to put the device into bootloader mode. Then after I'm done seeing what firmware it is on, I can't exit bootloader mode unless I upload a new firmware (or the same one back on). So allow a cancel/exit bootloader button within the uploader.

3) The companion software, ISOLoader, doesn't run from within the drive itself! It's just a blank screen. I like keeping all the software for a device, on the device. <side rant>What I've always dreamed of is for device manufacturers to include a 512 mb flash drive on every device (using "universal" mass storage drivers), then put the drivers for their device on that flash drive! I hate having to carry around a USB-Wireless Dongle, AND a flashdrive with the drivers for that dongle.</side rant>

4) On the ISOLoader, it's hard to tell what ISO is currently inserted. Place a read-only label with the contents of the /config/iso_filename.txt inside of the read-only label, so it's easy to know what is currently loaded in the ODD (Optical Disc Drive).

Mostly though, this is all small nitpicking things! It's a great device, and I love it! Just got it in the mail today, and I'm thrilled. I've dreamed of a device like this for a while now!

1) Configureable device identifiers. IE, Elegant ISOStick CDRom. This way we could change it to more closely emulate a "regular" cd-rom. Some software use this identifier, and it'd be nice to change it to what the software is expecting.

Hm, could you name some software that does this, and what it might expect? It seems surprising to me, because there are so many CD/DVD/BluRay drives--unless you mean it might try to reject isostick because it is a virtual drive (anti-piracy, etc).In any case, that would be possible to do.

2) When updating a new firmware, I don't know what firmware is currently loaded without having to put the device into bootloader mode. Then after I'm done seeing what firmware it is on, I can't exit bootloader mode unless I upload a new firmware (or the same one back on). So allow a cancel/exit bootloader button within the uploader.

I could definitely be clearer about this in the documentation and in the app -- you can simply replug your isostick and it will come back up as the same firmware you have loaded. However, I'll add some TODOs for a better way to display current firmware, as well as a Cancel button in the updater to tell it to jump out of the bootloader and into the already-loaded firmware, for ease of use.

It should be possible for me to have ISO Manager display the current firmware, using a similar technique to how isosel works. Something like: have ISO Manager create a file during initial setup, say, /config/version, and make it some arbitrary length, filled with nulls. Then, isostick firmware can be updated so that if it sees the host reading /config/version, it returns a string with its version instead of the nulls which are actually on the card.

This is basically how isosel works: when you have a bootable (per El Torito standard) disc loaded, when the host requests the Boot Catalog and the actual bootable code within the ISO, the isostick instead feeds it a fake Boot Catalog, and isosel.bin, respectively. After you make a choice, isosel is temporarily disabled until isostick notices those same locations being read again, then isosel is re-enabled for the next boot (next time isostick is enumerated as a USB device). That's done because isostick cannot detect when you are in an OS or BIOS, so it can't only show isosel, or only show the ISO.

EDIT: As a side note, I also have plans for a way to put the device into bootloader mode from the updater, without hitting that darn button. The button is hardwired so it will always work regardless though, in case something goes horribly awry.

3) The companion software, ISOLoader, doesn't run from within the drive itself! It's just a blank screen. I like keeping all the software for a device, on the device.

Whoops! Just fixed that and uploaded a new ISO Manager.

What I've always dreamed of is for device manufacturers to include a 512 mb flash drive on every device (using "universal" mass storage drivers), then put the drivers for their device on that flash drive! I hate having to carry around a USB-Wireless Dongle, AND a flashdrive with the drivers for that dongle.

I completely agree! Speaking of which, I plan for future firmware to at least show up as a flash drive if you have no card inserted, and it will have a little readme file explaining that you should put a microSD card in, and directing you to isostick.com for all the details and utilities. That is, if I can squeeze all that in the unused flash on the microcontroller!

4) On the ISOLoader, it's hard to tell what ISO is currently inserted.

Good call! It's on the to-do list now.

Mostly though, this is all small nitpicking things! It's a great device, and I love it! Just got it in the mail today, and I'm thrilled. I've dreamed of a device like this for a while now!

When you boot from your isostick, isosel will present you with a list of all your ISOs. From there you can pick any ISO you want and reboot into it. On the next boot you'll see isosel once again.We invite you to check the isosel page for all the details!

Um! there is no link to the isosel page it refers to.

Oh and one more.More Screenshots Please. Some videos would be great too. I see you have some on the main page and in the Download. It would be good to have a Screenshots page. That is one of the first things I try to find when looking into a product.

If any ISOs are larger than 4GB, ISO Manager will automatically split them.Split ISOs will show up as one file in the list for simplicity.

Is there a way the user will know this without reading it somewhere. How about the ISO Manager telling the user that a certain file that is bigger is splitted but being shown as a single file. Something visual.

so if you drag any files other than ISOs into the list, it will warn that those files will not be copied. If you find that using ISO Manager to copy all sorts of files to your isostick would be very useful, please let us know and we’ll consider lifting that restriction.

Are there any negative reason why ISO Manager cant be allowed to copy all sort of files to isostick. As a user you will more then likely find it easy to do it that way if you already have it open. Could be an advance option of sorts.

Recommend to the user where and how they can format that large exFAT card to FAT32.

Done, thanks!

More Screenshots Please. Some videos would be great too. I see you have some on the main page and in the Download. It would be good to have a Screenshots page. That is one of the first things I try to find when looking into a product.

Actually planning to whip up some videos this week Screenshots page is a good idea too *scribbles on the todo list*.

Um! there is no link to the isosel page it refers to.

Oh jeez, I totally forgot about that

Is there a way the user will know this without reading it somewhere. How about the ISO Manager telling the user that a certain file that is bigger is splitted but being shown as a single file. Something visual.

Hm, we were tossing around some ideas, like having the CD icon in the list be "split," but we thought some people might take that to mean "broken." It will tell you it's split in the tooltip if you hover over the ISO in the list, though... We figured a visual indication might be confusing, especially since split ISOs are treated the same as non-split ISOs by isostick -- there's no performance impact or anything.Any reason it should be called out?

Are there any negative reason why ISO Manager cant be allowed to copy all sort of files to isostick. As a user you will more then likely find it easy to do it that way if you already have it open. Could be an advance option of sorts.

Perhaps a checkbox to show all files vs. show just ISOs?Main reason was I was in a hurry to get something functional out there and unsure of the complications in showing all files Looking at it in more depth now, doing a proper file listing with drag'n'drop will be simple enough. I was a little concerned about clutter, but you're right: the more I use it, the more I think it would be nice to just have everything there. Another one for the ever-increasing todo list

Actually planning to whip up some videos this week Screenshots page is a good idea too *scribbles on the todo list*.

Hm, we were tossing around some ideas, like having the CD icon in the list be "split," but we thought some people might take that to mean "broken." It will tell you it's split in the tooltip if you hover over the ISO in the list, though... We figured a visual indication might be confusing, especially since split ISOs are treated the same as non-split ISOs by isostick -- there's no performance impact or anything.Any reason it should be called out?

What im not understading im guessing is how this works. Does it split the original file on the usb stick and then keeps a copy of the original file or does it get split when loading the ISO virtually only and nothing happens to the original ISO. Or is the original deleted when the ISO is splitted as mentioned. In view of this im not getting a good picture of how the split thing works. How about adding a representation of how many pieces the file is splitted into.

Perhaps a checkbox to show all files vs. show just ISOs?

Thats a good idea.

Main reason was I was in a hurry to get something functional out there and unsure of the complications in showing all files

Sounds reasonable.

Looking at it in more depth now, doing a proper file listing with drag'n'drop will be simple enough. I was a little concerned about clutter, but you're right: the more I use it, the more I think it would be nice to just have everything there. Another one for the ever-increasing todo list

Hm, regarding splitting: When you drag'n'drop an iso file into ISO Manager, it will copy it onto your isostick. If the file is >4GB, it will split it into as many files as necessary, each being at most 4GB (since that is the FAT32 limit). The original file is intact since it is just being copied to the stick, but ISO Manager is creating .iso.0, .iso.1, etc... files on the isostick, splitting it "on the fly." Of course, if the file is <4GB, it will just copy it as usual, no splitting.

When I add the ability to drag files out of ISO Manager to copy files *from* isostick, it will auto-join, so you get one big iso file again.

Hm, regarding splitting: When you drag'n'drop an iso file into ISO Manager, it will copy it onto your isostick. If the file is >4GB, it will split it into as many files as necessary, each being at most 4GB (since that is the FAT32 limit). The original file is intact since it is just being copied to the stick, but ISO Manager is creating .iso.0, .iso.1, etc... files on the isostick, splitting it "on the fly." Of course, if the file is <4GB, it will just copy it as usual, no splitting.

Thanks. I now have a better understanding of the way it works. How about adding this to the FAQ, and is there going to be a video demo of how this works ?

When I add the ability to drag files out of ISO Manager to copy files *from* isostick, it will auto-join, so you get one big iso file again.

'knightofoldcode', on 25 Oct 2012 - 16:38, said: 2) When updating a new firmware, I don't know what firmware is currently loaded without having to put the device into bootloader mode. Then after I'm done seeing what firmware it is on, I can't exit bootloader mode unless I upload a new firmware (or the same one back on). So allow a cancel/exit bootloader button within the uploader.

I could definitely be clearer about this in the documentation and in the app -- you can simply replug your isostick and it will come back up as the same firmware you have loaded. However, I'll add some TODOs for a better way to display current firmware, as well as a Cancel button in the updater to tell it to jump out of the bootloader and into the already-loaded firmware, for ease of use.

I second this request to allow a way to exit the bootloader mode via software.

Would it be possible to emulate 2 drives at once? We have an in-house Ghost image that is split over 2 DVDs. We boot up Bart PE and run Ghost which loads the image from the first DVD and then we have to switch DVDs half way.

Is the disk emulation locked due to hardware or can multiple ISOs be loaded at once?

Also planned is a way to specify a sequence of discs, like multi-disc installs. Ejecting the current disc would cause the next one in the sequence to be loaded. (original discussion)

We have an in-house Ghost image that is split over 2 DVDs.

It might be worth trying one giant ISO, if that's possible for you to do. The isostick can support just about any size ISO. ISO Manager will split the iso file automagically to fit on FAT32 (but it still acts like one single ISO file). If you're not on Windows you can split the ISO yourself as outlined here: http://reboot.pro/to...s-for-isostick/

Anyway, not sure if that makes sense for your workflow but might be worth a shot