[comp.sys.amiga.emulations] IBeM Setup

rodmar@gn.ecn.purdue.edu (Rodney L Martin) (03/04/91)

I am having one heck of a time getting IBeM to run at all!  Would someone
who has it working please post instructions, including messydos version and a
mountlist?  

I am running a LUCAS/FRANCES and messydos 1.30.  All I get is a cli prompt
after running IBeM.  It allocates the memmory, but does not run.  I also
had messydos installed in df0: and an msdos boot disk in df0:  Am I missing
something??

Thanks...

Rod

rsmith@uncw.UUCP (Ross Smith) (03/06/91)

rodmar@gn.ecn.purdue.edu (Rodney L Martin) writes:


>I am having one heck of a time getting IBeM to run at all!  Would someone
>who has it working please post instructions, including messydos version and a
>mountlist?  


>I am running a LUCAS/FRANCES and messydos 1.30.  All I get is a cli prompt
>after running IBeM.  It allocates the memmory, but does not run.  I also
>had messydos installed in df0: and an msdos boot disk in df0:  Am I missing
>something??

>Thanks...
  
   I simply followed the directions for the mountlist for both msh 1.3 and
the IBeM program, noting to use dostype 3 for the internal drive on my
3000 (remember to set the dostype in both the msh mountlist AND the IBeM
mountlist...).

   I then mounted them both, threw a 720k 3 1/2 DOS floppy in the internal
drive and ran IBeM, sucker booted right up.

   I too had problems originally getting started, mostly due to error
on my part... the quick black flicker then right back to the cli was
something I encountered before reading all the instructions on both msh
and IBeM (had never used messydos before trying out IBeM...) 

   Anyway, good luck, but like I said before the speed is dissapointing.
Having a 25Mhz 3000, and noting how slow it is, I wonder what it is like
on a 14Mhz '20? anyone out there have a 68020 care to share what they
experienced?
                                              Ross Smith


>Rod

DEB110@psuvm.psu.edu (Doug Bischoff) (03/07/91)

     What do you mean you mounted BOTH of them?  How can you do that? I'm quite
confused, but would like to try it still... first I need MSH, tho.  Where can I
get that?  PLEASE post mountlist entries for both of them!  Thanks.

-Bish

bjh@cbnewsj.att.com (bernard.j.hudson) (03/09/91)

Some comments from my test of IBeM on my A1000 16MHz 68020 LUCAS/FRAN computer.
It works for me and Norton 4.0 reports CI=0.8 times an original PC.
I think Transformer was CI=0.2 on a stock A1000.

1. IBeM is a IBM PC emulator (like Transformer) that requires no special 
   hardware except an Amiga with a 68020 or 68030 with 2M.
2. A Tryware version is available via FTP from abcfd20.  It is limited to
   15 minutes run-time.  The full version is $30, I think.
3. There is no startup error reports, so it gives a black screen and
   then just exits if the setup is bad.
4. It requires MessyDOS disk handler and works with 1.5 or 1.30(newer).
   To get started, edit the Mountlist down to just IBMA: and add
   Reserved=0 to the entry and change the Device = 1 for DF1:.
5. For a 2-floppy system, assign Devs: and L: to the MSH versions in RAM: or DF0:.
6. Verify that MSH: is working by mounting IBMA: (MSH1:) and listing DIR
   of PC floppy in IBMA: (DF1:).  I found it best to NOT manually
   mount IBMA: before running IBeM.  After getting MessyDOS working,
   reboot and setup again, but wait and let IBeM mount IBMA: when it runs.
7. Now start IBeM from DF0: and have MS-DOS boot floppy in DF1:.
8. Possible failures:  (always seems to be returncode 10)
   a. "Wrong Processor" (requires 68020; problems reported with A3000)
   b. "Unable to allocate memory" (requires 680201M free fast RAM)
   c. "Hard disk partion limited to 2M, Buy the full version" 
      (check that mountlist only has entry for single floppy IBMA:)
   d. Looks for DEVS:Mountlist and L:MessyFileSytem and exits
      (check that assigns for DEVS: and L: point to IBeM and MSH versions)
   e. Reads MSH: floppy, but exits  (make sure that DEVS: and L: are
      not on the same floppy drive as IBMA: because the PC boot floppy
      must be in place when IBeM is started. Check Device = 1 in Mountlist.)
   f. Exits back to CLI after 15 minutes (normal for this version)


I hope this helps.  I have no connection with the author.        .....BJ
bjh@mtgzz.ATT.COM