As I did all this testing by running Makedisk, writing USB, and then booting into IFL from USB, I found it takes quite a while. I was wondering if you have internally created a way to build IFL boot media directly to a .vdi or .vmdk virtual image so they could be tested within your main development environment, rather than booting back and forth?

As I did all this testing by running Makedisk, writing USB, and then booting
into IFL from USB, I found it takes quite a while. I was wondering if you
have internally created a way to build IFL boot media directly to a .vdi or
..vmdk virtual image so they could be tested within your main development
environment, rather than booting back and forth?

as far as what smbtree finds, the linux tools can be flaky, as it is now, if
it doesn't find servers it used to, you may need to edit /etc/samba/smb.conf
and remove the max protocol line. But you can manually enter the name
still. The version used is the last one that actually partial works, the
latest versions don't work well at all.

"timg11" wrote in message news:14208@public.image...

Has this been fixed in the 3.11 release of IFL? Specifically, has the
version of SMBtree used by the IFL tools been updated so it can work with
SMB v2?