Why can't I get my 1.3 Hard drive to boot or even mount?
Gordon Gilbert
I just purchased Amiga Forever and downloaded the latest UAE. I
just transferred my Amiga 3000's WB1.3 partition (leftover from the
soft kickstart days, now normally booted with a softbooter since I
have 3.1 roms in the 3000 now) over to the PC via null modem cable,
but I'm find that I can't get WinUAE to boot from that partition.
In fact, I can't seem to get WinUAE to mount a hard drive partition
PERIOD under 1.3, even booting from a floppy! What's going on
here? I know I saw a reference to booting hard partitions under 1.3
in the UAE (not WinUAE) docs somewhere. Am I to believe that this
"Ultimate Amiga Emulator" has NO support for hard drives under 1.3?
I find that difficult to believe. I might be able to understand
lack of support for 1.2, but HD under 1.3 ought to be a given
considering 1.3 was the first version of the OS to support HD
auto-booting. I ought to be able to at least MOUNT a HD under 1.3
even if I can't boot from it (for whatever stupid reason). What
gives? Is there something I'm doing wrong???
--
- Gordon Gilbert | g...@sssnet.com -
- Visit The Audiophile Asylum for CD and DTS CD Reviews with -
- Sound Quality Ratings at http://pages.sssnet.com/glg -
Robert Templeton
> just transferred my Amiga 3000's WB1.3 partition (leftover from the
> soft kickstart days, now normally booted with a softbooter since I
> have 3.1 roms in the 3000 now) over to the PC via null modem cable,
> but I'm find that I can't get WinUAE to boot from that partition.
> In fact, I can't seem to get WinUAE to mount a hard drive partition
> PERIOD under 1.3, even booting from a floppy! What's going on
> here? I know I saw a reference to booting hard partitions under 1.3
> in the UAE (not WinUAE) docs somewhere. Am I to believe that this
> "Ultimate Amiga Emulator" has NO support for hard drives under 1.3?
> I find that difficult to believe. I might be able to understand
> lack of support for 1.2, but HD under 1.3 ought to be a given
> considering 1.3 was the first version of the OS to support HD
> auto-booting. I ought to be able to at least MOUNT a HD under 1.3
> even if I can't boot from it (for whatever stupid reason). What
> gives? Is there something I'm doing wrong???
I just went through this mess myself. It requires a little finess in the
settings to get the thing to see the "hardfile" drive. A "hardfile", as
compared to a "directory", must be used to gain access to a virtual
harddrive in UAE using KS1.3.
For WinUAE configuration, these are required:
* Misc.:
"AutoConfig" must be turned on.
* Hard Drives:
"Add PC Drives at Startup" should be turned off.
Click "Add Hardfile". A window opens. Under "New Hard File", type in a
drive size in bytes in multiples of 1048576 bytes. For instance, 8 Megs =
8388608 and 32 Megs = 33554432. Click on the "Create" button and give it a
file location and name for the new "hardfile".
The "Hard File Settings" must be (at these settings work) Surfaces=1,
Reserved=1, Sectors=32, Block-Size=512, Read/Write=checked. Click the
"Okay" button to finish. A drive should appear in the listing as DH0 with
the path to the hardfile that you just created.
Save your WinUAE configuration settings.
===============================================
Before you can use this newly created hardfile, you must modify the
devs:mountlist and s:startup-sequence files on your Workbench 1.3 diskette
(adf, that is - make a copy of the adf because I've had the misfortune of
saving my mountlist and ending up with an empty file for no particular
reason). Boot up WinUAE with this disk, open a shell in Workbench, and type
"ed devs:mountlist". Add the following entry to the end of the mountlist
(change HighCyl = 2047 for 32 Meg hardfile):
UAE0:
Device = uaehf.device
Unit = 0
Flags = 0
Surfaces = 1
BlocksPerTrack = 32
Reserved = 1
Interleave = 0
LowCyl = 0 ; HighCyl = 511
Buffers = 5
DosType = 0x444F5300
BufMemType = 1
#
Hit the ESC key, then "x", followed by ENTER to save and quit.
Hit F12, select the Misc. tab, click on the "Reset WinUAE" then "Okay"
buttons. The Amiga resets. To verify that everything has worked, open a
shell, type "mount uae0:", then type "cd uae0:" (it will complain; ignore),
and a new drive should appear on the Workbench. You must format this drive
in order to use it. Do so now.
Now type "ed s:startup-sequence" in the shell. The very first executable
lines in your startup should be:
mount uae0:
cd uae0:
The second line is needed, for some unknown reason, to make the device mount
completely and become available to the operating system. Save this and quit.
Reset WinUAE. Fun, ain't it ;)
===============================================
After you have successfully done this, we can concentrate on getting those
files you transferred into the hardfile. e-mail me once you have done this
or if you run into a brick wall.
Regards,
Robert Templeton
the_...@my-deja.com
> (change HighCyl = 2047 for 32 Meg hardfile):
>
> UAE0:
> Device = uaehf.device
> Unit = 0
> Flags = 0
> shell, type "mount uae0:", then type "cd uae0:" (it will complain;
ignore),
> and a new drive should appear on the Workbench.
The very first executable
> lines in your startup should be:
> mount uae0:
> cd uae0:
This is WRONG in current releases.
Hardfile names have been changed to DHx: from a version of 0.8.???
onward.
So you need to mount dh0: NOT uae0:
Greetings
Andreas aka [the]_janus
Sent via Deja.com http://www.deja.com/
Before you buy.
the_...@my-deja.com
I think the problem is how we should define 'auto-booting'.
An auto-booting hardfile for me, that is a hardfile that is able to
boot with only a rudimentary WB installed on it.
I think this is only possible under Kickstart 2.0 or higher.
Also Fellow does *NOT* display your hard file at all on the
configuration screen if you're using Kick < 2.0, because its docs say
it's simply not possible at all.
Now I see it *is*.
Hummm...maybe I should try it with a game that I only own on floppy
disks : Cruise for a Corpse.
The original disk version runs fine under Kick 1.3, but if you install
the whole thing to hard disk, you *will* need 2.0. No buts.
*now cluelessly looking at both of you*
Regards
Andreas
Robert Templeton
<the_...@my-deja.com> wrote in message news:80ri0f$qea$1...@nnrp1.deja.com...
> Before you buy.
YOU ARE WRONG!
I have one running in version WinUAE 08.8 R8 rebuild. Do you? Try it.
Regards,
Robert Templeton
Gordon Gilbert
>
> Hi Robert, hi Gordon,
>
> I think the problem is how we should define 'auto-booting'.
>
> An auto-booting hardfile for me, that is a hardfile that is able to
> boot with only a rudimentary WB installed on it.
>
> I think this is only possible under Kickstart 2.0 or higher.
That may be the case with the various Amiga emulators but I
GUARANTEE you that on REAL Amigas, you can boot from your Hard Drive
(no FLOPPY required and NO "mounting" required) under AmigaDos 1.3.
With AmigaDos 1.2, you needed to mount your hard drives as was
described in this thread, but that should NOT be necessary under
AmigaDos 1.3 or later. I have an Amiga 3000 and it originally came
with soft-kickable roms and I could boot from two different hard
drive partitions with two different rom sets and that included
AmigaDos 2.04 and AmigaDos 1.3. Both booted off the hard drive
fine. I have AmigaDos 3.1 (hard rom) on my A3000 now and I can only
boot 1.3 with "softboot" program and it doesn't recognize my 1.3
partition (it tries to boot off my 3.1 one!) because the A3000 used
a special method to boot from those partitions, but I can use a
floppy disk to redirect it. But under emulation, I should be able
to just select my 1.3 partition hardfile (and the work hardfile) and
it should be able to boot from 1.3 and automount the work
partition. It did exactly that on my A3000 (and still does once
reassigned to System1.3 with a floppy. I don't have to mount my
other hard drives under 1.3!!!)
I don't know where all these wrong ideas came from, but it seems
like the people that made the UAE emulator never really dealt with
1.3. It should be fully auto-bootable and auto-mounting for hard
drive partitions (hardfiles on emulator).
I also hope they're working on fixing sprite collisions with
backgrounds. Archon is not very playable because the objects that
are there for you to hide behind let firepower pass right through!
Also, UAE seems to default as a PAL Amiga system. I believe this
is causing some problems with some of my games (NTSC). The screen
displays get glitched because they're too long and of course the
speed would be off too (run NTSC stuff too slow because of the 50Hz
vs. 60Hz issue). Is there a way to select whether it defaults to
PAL or NTSC? On my Amiga 3000 there is a jumper on the motherboard
that selects whether it defaults to PAL or NTSC. There should be a
way to switch it in the emulator. The CCS64 and Vice64 emulators
allow such switching for C64 games. Amiga emulators should provide
that option as well, IMO.
> Also Fellow does *NOT* display your hard file at all on the
> configuration screen if you're using Kick < 2.0, because its docs say
> it's simply not possible at all.
Well, it sounds like the guy that made Fellow either doesn't know
how to do it or didn't know any better.
> Now I see it *is*.
>
> Hummm...maybe I should try it with a game that I only own on floppy
> disks : Cruise for a Corpse.
> The original disk version runs fine under Kick 1.3, but if you install
> the whole thing to hard disk, you *will* need 2.0. No buts.
On the Amiga or under emulation? In any case, there were some
games that were installable on hard drive only if you had the AGA
version (e.g. Pinball Fantasies) and so I guess there could be some
games that could only be installed on hard drive under 2.0+. But I
had plenty of games that would run off the hard drive on both 1.3
and 2.0/3.1. Examples? Death Knights of Krynn, Battle Chess,
Tetris, etc.
the_...@my-deja.com
>
> YOU ARE WRONG!
>
> I have one running in version WinUAE 08.8 R8 rebuild. Do you? Try
it.
>
> Regards,
>
> Robert Templeton
>
Hi Robert,
1. what is a 08.8 R8 _rebuild_ ?
Did you build it yourself, is that what you mean?
2. OK, maybe I'm _partly_ wrong.
As far as I could perceive it, I only saw DHx: drives when booting the
Hard disk with Kick 2.0 in the 'Hardfiles' tab.
Maybe the device is _internally_ the same as it was in earlier UAE
releases (that is : UAEx:) and it's only _displayed_ DHx:
But this cannot be because I booted from a FFS floppy under Kick 3.0
WITH the hard file inserted. Then I did a '^C' in WB 3.0 (CTRL-D)
and I typed cd uae0: - it did NOT work!
Then, I typed 'cd DH0:' - this *did* work!
So ... maybe we're talking about two different things here...
Regards,
Andreas
Robert Templeton
<the_...@my-deja.com> wrote in message news:80uitn$4m$1...@nnrp1.deja.com...
> Hi Robert,
>
> 1. what is a 08.8 R8 _rebuild_ ?
>
> Did you build it yourself, is that what you mean?
This is Brian's latest compile of R8, not completely upgraded because he
only changed compiler settings to remove buggies and increase execution
speed.
> 2. OK, maybe I'm _partly_ wrong.
> As far as I could perceive it, I only saw DHx: drives when booting the
> Hard disk with Kick 2.0 in the 'Hardfiles' tab.
>
> Maybe the device is _internally_ the same as it was in earlier UAE
> releases (that is : UAEx:) and it's only _displayed_ DHx:
>
> But this cannot be because I booted from a FFS floppy under Kick 3.0
> WITH the hard file inserted. Then I did a '^C' in WB 3.0 (CTRL-D)
> and I typed cd uae0: - it did NOT work!
> Then, I typed 'cd DH0:' - this *did* work!
>
> So ... maybe we're talking about two different things here...
I use only "directory" hard disks under kick 2.0 and up. But I needed a
hard disk under kick 1.3 and by reading Brian's original Readme it was
determined that the only course of action was to use a "hardfile" hard disk
which had to be mounted with an entry in the devs:mountlist on my Workbench
1.3 adf diskette. I followed the given instructions and was partially
successful. After some fiddling, it finally worked. The "mount uae0:" is
mentioned in the readme, but the "cd uae0:", which works for me, is not.
Although the mountlist entry is UAEx: using uaehf.device, the hardfile that
one creates in the WinUAE config is listed there as DHx:. I believe that I
have seen the change from UAEx: to DHx:, but, in my case, DHx: didn't appear
to work. Nonetheless, it appears that UAEx: compatibility is still there
and a scan of the source code reveals a uaehf.device and mention of UAEx:
hardfiles.
I think that in your trial case, it worked the same as some of my
experimentation. Since the drive is mounted as dh0:, cd uae0: will not work
(?).
Lil' Miss Newbie
please, PLEASE (with cherries on top), post a nice, step by step guide to
mounting the thing in the first place??? (as you've guessed by the name, I need
my info in small, bitesized chunks). It's important to me especially as I read
thru your initial post and realised how close I'd actually come to trashing my
old man's shiny 8Gb PC harddrive, for the sake of mounting an Amiga 40Mb one
(Format SCSI unit 0 - I think not!! I think my life'd be substantially shortened
if I did that)
Cheers!!