Zalman ZE350 "Save/Lock Image"

[Mainstay]

Hi All,

Just added a new Zalman ZE350 to the fleet. I have the ZE300 and love it.

On the ZE350 I have all my images loading just fine and the directory structure is correctly loading etc.

However, I cannot seem to Save or Lock the current image so that the next time I plug it in that last image is the default image.

On the ZE300 I would hold the backup button for 2-3 seconds and then it would show a "saving data..." followed by a "plug out".

This isn't happening here.

The backup button works nicely... but the functionality of locking the image is missing.

Or am I doing it wrong?

Physically speaking, I would be hard pressed to tell the difference between the units.

(firmware has been updated to 1.1).

Any thoughts?

Thank you!

--Matthew

 

[omnichad]

Were you ever able to resolve this? I see that 2.0 firmware is out, but their download page isn't working today.

I have a Zalman ZM-VE200 in my car, but I want a second one for my work bench. I am leaning toward buying the (more expensive) iodd 2351 that this is based off of, which does save your current ISO. Though it would be nice to have SATAIII support since I will be putting an SSD in this one.

 

[Mainstay]

No - this is a bit of a bug bear for us.... I have to either be SUPER quick with my directory navigation or somehow pause the boot sequence (which sometimes also requires me to be quick).

I have not revisited the firmware... may give that a shot.

Will let you know how that goes.

 

[NJW]

... somehow pause the boot sequence ...

Entering BIOS will keep the Zalman powered, so you can select the image you want, then save & exit from the BIOS to reboot. Alternatively, select the boot manager, make the Zalman selection, then continue.

 

[omnichad]

save & exit from the BIOS to reboot. Alternatively, select the boot manager, make the Zalman selection

From my own experience with the ZM-VE200, that is not always the case. There are a lot of computers that cut power to everything at the moment of a supposedly warm reboot - including the CPU fan, USB ports and all. And others, the boot menu will only show drives detected as bootable.

There was a recent computer I worked on that did BOTH - the ZM-VE200 didn't even work. I had to run a USB Y cable to a nearby desktop with an extension just to get it to boot from it. Even setting the virtual CD-ROM as the primary boot device didn't work, because the computer POSTed too fast to allow the Zalman drive to both spin up and mount an image (it was detected as empty).

 

[NJW]

There are a lot of computers that cut power to everything at the moment of a warm reboot - including the CPU fan, USB ports and all.

Agreed, they do exist, but not so much with newer machines. Separate power to the Zalman is the only solution there, as you note.

And others, the boot menu will only show drives detected as bootable.

If the Zalman is configured as CD-ROM, it should be detected, even if the .iso image is not the right one. (But I only have the VE300, so there may be differences.)

... because the computer POSTed too fast to allow the Zalman drive to even spin up.

Zalman + SSD.

 

[omnichad]

Agreed, they do exist, but not so much with newer machines. Separate power to the Zalman is the only solution there, as you note.

This was a brand new laptop, configured for secure boot by default.

If the Zalman is configured as CD-ROM, it should be detected, even if the .iso image is not the right one. (But I only have the VE300, so there may be differences.)

It was detected as empty because the iso image didn't even load yet. Stupid boot menu hides empty drives. That one automatically loads the last ISO.

Zalman + SSD.

That's the plan for my next one - Zalman or iodd + SSD - which is why I resurrected this old thread. An SSD would decrease the power requirement, but with this computer - the Zalman firmware may not load fast enough (don't know, never tried SSD in one).

 

[Mainstay]

I see that 2.0 firmware is out

Upgraded to 2.0 (bizarrely simple to do) and no change in behavior. I had a really persnickety Asus on the bench today and I simply could not get it to hold at boot selection so I had to borrow my colleagues VE300. Instantly booted to desired ISO. Damn you Zalman! Just when I learn about you you mess up your product line.

 

[omnichad]

Looks like I'll have to move on to the IODD. Here is the product page in case you want one too:
https://www.amazon.com/Iodd-Iodd2531-Black-Virtual-Enclosures/dp/B00TDJ4BJU

It works very similarly to the earlier Zalman drives and is the same hardware on the inside - just a bit different firmware. I haven't ordered mine yet, but the reviews are really good. Apparently Zalman was the copycat all along.

 

[HCHTech]

I have 3 or 4 Zalmans - I really wanted to like them, but there were too many cases where you couldn't get the machines to boot from them, so they sit in my drawer unused now - with the rest of the tech in that little land of misfit toys.. Now, there are way fewer times I need to boot from an image, not zero, but fewer. I might get an IODD just to check it out.

 

[Mainstay]

My IODD 2531 just arrived. I took my HD out of my ZE350 and popped it straight into the IODD. All images and interface exactly the same... wonderful!

Talk about a rip-off - the Zalman unit is indistinguishable from the IODD.

For anyone with a ZE350 and trying to get the image to save/lock.... try hold the DOWN toggle for 5 seconds... see if that works.

Otherwise - IODD all the way.

 

[FrkaServis]

My IODD 2531 just arrived. I took my HD out of my ZE350 and popped it straight into the IODD. All images and interface exactly the same... wonderful!

Talk about a rip-off - the Zalman unit is indistinguishable from the IODD.

For anyone with a ZE350 and trying to get the image to save/lock.... try hold the DOWN toggle for 5 seconds... see if that works.

Otherwise - IODD all the way.

I use ZM-VE350 and in new Firmware Ver. 2.02 last used ISO stay auto locked.