14 Jun
2007
14 Jun
'07
11:02 a.m.
Hi
Yes I got past that afer a bit of trying.
I have both Ricoh and ASUS DVD and CD R/RW Drives
I had to change the extension from .img to .nrg as raw data or not
Nero would not look at either of my drives as .img is not supported.
It asks about block sizes around 2k. VMS CD are 512.
My first attempt did not boot. I'll try again to-night
Rod
-----Original Message-----
From: cctech-bounces at classiccmp.org
[mailto:cctech-bounces at classiccmp.org] On Behalf Of Antonio Carlini
Sent: 14 June 2007 08:41
To: 'General Discussion: On-Topic and Off-Topic Posts'
Subject: RE: Boot CD - The last LAP
Rod Smallwood wrote:
2. Nero and imgBurn wont read
the image file.
I'm sure I used Nero when I did this. I'm also sure that if ImgBurn
("Image Burn") cannot do it then it should be renamed :-)
I think the sequence with Nero is something like:
Start->Programs->wherever Nero Burning ROM lives
Cancel the initial screen that helps you determine whether you are
burning a CD or DVD or whatever
Recorder->Burn Image
Select "All Files" (make sure yours is called .img or .bin)
On the "Foreign Image Settings" leave it as "Data Mode 1" and tick
"Raw Data"
Try a CD-RW until you find the right incantation.
I would download one of the Freeware CDs from the HP VMS website and try
that image, so at least you know you have a good ODS-2 image at the
start.
An RRD42 will not (IIRC) cope with a CD-RW ... so you may need to use
the Yamaha to start with (assuming it will).
Antonio
14 Jun
14 Jun
12:12 p.m.
On 6/14/07, Rod Smallwood <RodSmallwood at mail.ediconsulting.co.uk> wrote:
Hi
Yes I got past that afer a bit of trying.
I have both Ricoh and ASUS DVD and CD R/RW Drives
I had to change the extension from .img to .nrg as raw data or not
Nero would not look at either of my drives as .img is not supported.
The joy of operating systems with enforced filename extensions. :-P
It asks about block sizes around 2k. VMS CD are 512.
That will be the key - to get whatever tool you use to write 512-byte
blocks, not 2048-byte blocks.
As I am not a regular Windows user, I can't suggest any Windows tools,
but you have, I think, identified the crux of your requirements -
user-specifiable block size.
-ethan
1:12 p.m.
On 6/14/07, Ethan Dicks <ethan.dicks at gmail.com> wrote:
As I am not a regular Windows user, I can't suggest any Windows tools,
but you have, I think, identified the crux of your requirements -
user-specifiable block size.
I could not get Roxio CD Creator to burn a VMS boot/install CD image.
I used CDBurn ( http://go.microsoft.com/fwlink/?LinkID=16544 ) which
worked fine.
I was able to boot the resulting CD using a Plextor CD-ROM switched
for 512-byte blocks with a Dilog SQ706A SCSI MSCP controller in a
MicroVax-II
1:34 p.m.
Ethan Dicks wrote:
The joy of operating systems with enforced filename
extensions. :-P
To be fair, this is Nero assuming or enforcing! I can usually override
Windows' defaults.
That will be the key - to get whatever tool you use to
write 512-byte
blocks, not 2048-byte blocks.
You cannot do this. The CD is always 2048 bytes per block. It is the
drive
that pretends that instead of N 2K blocks you have 4*N 512 byte blocks
so it looks like a disk. This made life easier in the earlier days for
the OpenVMS and Solaris (and IRIX?) driver writers ... and threw the
rest of us another bump to trip over in the years to come!
Antonio
2:31 p.m.
On 6/14/07, Antonio Carlini <arcarlini at iee.org> wrote:
Ah... I had thought that the underlying filesystem was part of the
equation, not that the drive did all the work.
Ethan Dicks wrote:
Strictly speaking, yes... but extension rigidity is a Windows mentality.
The joy of operating systems with enforced
filename extensions. :-P
To be fair, this is Nero assuming or enforcing! I can usually override
Windows' defaults. That will be
the key - to get whatever tool you use to write 512-byte
blocks, not 2048-byte blocks.
You cannot do this. The CD is always 2048 bytes per block. It is the
drive that pretends that instead of N 2K blocks you have 4*N 512 byte
blocks so it looks like a disk. This made life easier in the earlier days for
the OpenVMS and Solaris (and IRIX?) driver writers ... and threw the
rest of us another bump to trip over in the years to come!
I have worked with plenty of "starts up in 512-byte-block mode" issues
with old SCSI drives and Solaris - it does make boot code trivial
because you don't have to worry about the drive's block size. It was
nice with later versions of boot ROMs and such that knew that they
could and should send a packet to tell the drive to switch to
512-byte-block mode, removing the need for special models of drives
with mode jumpers.
Honestly, though, I haven't had to worry about it (except when playing
Software Archaeologist) in a long time, but then I don't burn ODS
disks often.
-ethan
1:31 p.m.
Rod Smallwood wrote:
Hi
Yes I got past that afer a bit of trying.
I have both Ricoh and ASUS DVD and CD R/RW Drives
I had to change the extension from .img to .nrg as raw data or not
Nero would not look at either of my drives as .img is not supported.
I don't know what you are doing wrong, but telling it it is an NRG file
is
incorrect. That's a Nero-internal format. You need .bin or something ...
I used .img when I did it. I've no idea why nero "won't look
at either of your drives".
It asks about block sizes around 2k. VMS CD are 512.
The block size on a CD is _always_ 2048. No exceptions. Ever.
Some drives will pretend that the CD is 512 byte blocks and
deliver based on that fiction. The CD is still 2048 bytes.
Antonio
2:32 p.m.
On 6/14/07, Antonio Carlini <arcarlini at iee.org> wrote:
Rod Smallwood wrote:
I've run into that in the past with Nero... .iso tends to be an
acceptable extension to most burning programs, IIRC.
-ethan
Hi
Yes I got past that afer a bit of trying.
I have both Ricoh and ASUS DVD and CD R/RW Drives
I had to change the extension from .img to .nrg as raw data or not
Nero would not look at either of my drives as .img is not supported.
I don't know what you are doing wrong, but telling it it is an NRG file
is incorrect. That's a Nero-internal format. You need .bin or something ...
I used .img when I did it. 
5:38 p.m.
On 14/06/07, Ethan Dicks <ethan.dicks at gmail.com> wrote:
I've run into that in the past with Nero... .iso
tends to be an
acceptable extension to most burning programs, IIRC.
I've definitely used Nero to burn *.img files. BUT I run windows with
"hide file extensions" turned OFF (i.e. - show them! It's in Folder
Options under View on any windows explorer window.) Then change
"files of type" to "All files", and it will magically appear.
7:01 p.m.
The problem with that is if you rename files and forget to include the extension you will
have problems later.
So, I suggest you turn "hide file extensions" on afterwards... unless you know
all your file types in ASCII - luckily the files I goofed on were image files (.BMP and
.JPG) so I used Notepad to view them, saw the ASCII text in the beginning of the files and
added the appropriate extensions ("JFIF" is a type of .JPG file and
"BM" is a bitmap image). All fixed then :)
Regards,
Andrew B
aliensrcooluk at yahoo.co.uk
Rob <robert at irrelevant.com> wrote: On 14/06/07, Ethan Dicks wrote:
I've run into that in the past with Nero... .iso
tends to be an
acceptable extension to most burning programs, IIRC.
I've definitely used Nero to burn *.img files. BUT I run windows with
"hide file extensions" turned OFF (i.e. - show them! It's in Folder
Options under View on any windows explorer window.) Then change
"files of type" to "All files", and it will magically appear.
9:42 p.m.
Hi,
So, I suggest you turn "hide file
extensions" on afterwards....
Actually, I have to disagree with that statement *MOST STRONGLY*!
THE VERY FIRST THING YOU SHOULD DO AFTER INSTALLING WINDOWS (aside from
reformatting and installing a "real" OS) IS TO _TURN_OFF_ "Hide file
extensions", AND LEAVE IT OFF!!!!!!!!!
For years, one of the biggest security problems with Windows has been this
utterly ridiculous hiding of file extensions; more systems have been
infected with trojans and virii due to executable files masquerading as
simple text files etc than by almost any other method....
If you have file extensions showing, you can instantly see when a file isn't
what it claims to be.
THERE IS NO GOOD REASON *WHATSOEVER* FOR HAVING FILE EXTENSIONS HIDDEN!
TTFN - Pete.
9:16 p.m.
Hi,
I don't know what you are doing wrong, but telling
it it is
an NRG file is incorrect....
Errm, in my experience NERO will, most of the time, figure out what the file
you're feeding it is, even if the extension is wrong.
Well, v5.5.x used to anyway....this may no-longer be the case.
....I used .img when I did it....
With NERO?
I just fired up my current copy, v6.6.1.4, and that doesn't appear to accept
".img" format images.
TTFN - Pete.
15 Jun
15 Jun
3:29 a.m.
Ensor wrote:
I just fired up my current copy, v6.6.1.4, and that
doesn't appear to
accept ".img" format images.
I use V6 too. Fire it up. Hit cancel (to eliminate the "what kind of
CD/DVD
do you want to create" thing), Recorder->Burn Image, down arrow on the
"Open" dialog "Files of Type" box and select "All files".
Click on
a .img file and select the right parameters on the foreign image box.
AFAIK it just burns the raw data right onto the CD in mode 1 (or
whatever mode you choose).
Antonio
6226
days inactive
6227
days old
11 comments
7 participants
participants (7)
-
aliensrcooluk＠yahoo.co.uk -
arcarlini＠iee.org -
classiccmp＠memory-alpha.org.uk -
ethan.dicks＠gmail.com -
glen.slick＠gmail.com -
robert＠irrelevant.com -
RodSmallwood＠mail.ediconsulting.co.uk