[Info-vax] InfoServer 150

Bill Gunshannon bill.gunshannon at gmail.com
Sat Jan 26 21:18:36 EST 2019


On 1/26/19 7:33 PM, Scott Dorsey wrote:
> Bill Gunshannon  <bill.gunshannon at gmail.com> wrote:
>> Not doing this from the command line.  I have three GUI based apps
>> and they all do it wrong.  Apparently they all see something wrong
>> with the images and refuse to just burn the data to a CD/R.
> 
> They see a file that isn't a .iso file and like a good gui they figure
> you want to put that file into an ISO filesystem.  Rename the file to
> .iso and Brasero will do what you expect.

No, actually it won't.  I tried it.  And Windows doesn't see it as
a valid .iso either so I am guessing Brasero knows what it is saying.

> 
> THIS is why you should use the command line.

The command line can't make the file format correct.

> 
>> But these images are not .iso.  And just renaming them as one site
>> recommended doesn't help.
> 
> The .iso is a straight disk image, what you'd get if you did a dd from the
> raw disk device.  Your .img file is the same.

Then the only possibility is that the files are corrupt.  We will
see when I get the Freeware 8.0 stuff unzipped on VMS.

> 
> Now, you have a second problem on Windows, in that you're using something
> that checks to see that it's a recognizable filesystem, which it is not.
> Because Windows doesn't know anything about VMS filesystems.

Why would it care about the file system if it is writing an image
to the disk?  Windows has happily written Plan9 and QNX and OS9000
and Ultrix and Linux and BSD.  Why would it suddenly be looking at
the contents of the ISO image just because it was Files-11?

bill





More information about the Info-vax mailing list