Conference hydra::amiga_v1

>>>Question: Should I partition my Hard Disk and create IBMpc.par
>>>          all by itself in one partition? Would that work?
             ******************************

Sounds like you are somehow using the same space on the disk for both 
operating systems and stomping all over each others directories.  Set up the 
two partitions making sure you aren't overlapping cylinders 

           PAR1_hi-cyl + 1 = PAR2_lo-cyl

Sorry, I don't own a bridge board to be able to give you a definative answer 
but your "ALL BY ITSELF" statement would have me concerned.

	Dick

    RE: .1
    
    	Hi Dick,
    
    I don't see anything wrong by installing MSDos on an AmigaDrive.
    The Amiga sees it as one pretty large file (up to the total capacity
    of the hard disk).  On the Amiga side mine is called :
    	"IBM:s/IBMpc.partition" but it can be called any name you want.
    
    Anyway, I re-partitionned my disk and reserved half of it for IBM:
    the other half is splited in DH0: (26 cyl system/boot non FFS disk) and
    the rest (cyl 28 to 305) is a "FastFileSystem (FFS) disk" (Used in WB
    1.3) (Much faster than normal format...)
    
    I would've liked if Comodore has the PC/XT software compatible
    with the "FFS" disks.  The AREAD and AWRITE command do not work
    properly on those.  Also, Janus do not seems to work with FFS's.
    I can transfer/use the /XT only on the DH0: or IBM: partitions.
    
    Anybody heard of a newer version or PCBridgeboard software update
    compatible with Workbench 1.3/FFS disk format?
    
    To close the problem stated in .0,  the solution is to:
    1) copy the same file/directory twice, or
    2) fill up the disk, erase it then use it.
    
    Possible explanation:
    It seems that if you add file to the hard disk and thus 
    requiring the amiga file to GROW, it does NOT copy properly.
    If you delete it, then re-do the copy, it works fine...
    (the file being the right size to start with).
    I still have to verify this possible explanation of the
    problem, but so far...
    Some program badly copied may crash the XT, some give an
    assortment of error messages.  I am surprised that nobody
    ever encoutered the problem.
    
    

    Vince.

Re -1

Sorry about my .1 reply. I didn't realize that the Amiga handles a MS-DOS disk
the same way as a VAX does with DECnet-DOS from a VAXmate. This business of
one operating system storing and expanding a file it doesn't understand on 
behalf of another operating system is garbage.

Just out of interest, is there a way to get your MS-DOS file to allocate the 
entire MS-DOS partition from some initialization sequence without having to
fill it with files? ( e.g. a program to write a partition sized file and then
delete it so that in the future, you won't require the partition to expand 
when you add files to it )  Seems to me that if this is the only way around
this problem of file expansion, it should have been documented somewhere.

	Dick

    Just to be precise:
    
    AREAD/AWRITE work well with FFS/disk on the Amiga side ( just did a 
    couple of floppies).

    Just a question
    
    Where is AREAD/AWRITE ??? I was looking for it yesterday  and I
    could not find (on the original CMB MS-DOS system disk).
    
    can somebody upload  them
    
    thanks
    
    ...gss...

    re -.1
    
    The Aread/Awrite progs are on the GWBasic floppy you got
    when you bought the BridgeCard.  I think they ran out of
    space on MSDos system floppy.
    
    re -.2
    
        I havent tried on FFS floppies, just on FFS hard disk.
    It is also possible that I messed up some commands.  I will
    try again soon.   Anyway, the result I got was a file on the
    Amiga hard disk with 0 (zero) byte size and a date that look
    like 99-DEC-9999.  If I try to print it, it send me a system
    message stating that the file is being opened by an other
    process. (or some message close to that)... (the file I
    tried to copy was text, Autoexec.bat)

    
    
Vince.

I got problems again with the BridgeCard/HardAmigaDisk combo.

Conclusion: the IBM works with an amiga hard disk... for half an hour
            average, then wipes or corrupt your MS/Dos directory(ies).

Hit "return" for more details, if interrested.


I first tought some programs may use some memory location used to
communicate with the Amiga side (PCdisk) and corrupt this bank
with either graph data or junk, telling it to corrupt the
hard disk directory??? I think I was wrong.

I was trying to analyse what is going wrong, here are some
bugs I found and the steps I took.

1) Power on Amiga (Boot Amiga Dos on Hard disk)
2) Double click PC icon, PCDisk and PCMono.
3) Boot MS/Dos on the 5�" (Autoexec bring me to Hard disk C: by
                           the JLINK program.)
4) In C:\UTILS I copied 5 PCTOOLS programs (including PCRESTOR.EXE)
5) I tried to start PCRESTOR.EXE and got invalid command message
   Just like if the program was not there at all.
   Did a C:\UTILS> DIR and all the files were there.
   Did a COPY again of only the restore utility.
6) typed pcrestor again and sure enough it worked...
   (4 programs out of 5 got copied properly)

My wife then tried to copy Word perfect (French MSDOS version)
Looked good so far.  Typed C:\WP> WP 
It worked, she exited then went to the Dbase directory and got
fatal drive not Ready, the directory was messed with... The
hard disk started to seek like crazy, even after rebooting 
the IBM (Ctrl/Alt/Del).  To stop it we had to reboot the whole 
Amiga. (Ctrl/Amiga/Amiga)

I guess I'll have to spend more $ for a *REAL* IBM 20 Meg. hardcard.

I beleive the JLINK.EXE (and probably the ADISK.EXE too) are
non functional.  I give up, I will write to Commodore soon.
They should not release non functional programs.

I also did more testing with Aread/Awrite, using the SAME
commands, sometimes it works, sometimes it doesn't. I have
never seen it failed on 3�" floppies yet.

MAYBE it's working OK with the Amiga floppies, MAYBE it's
working great with a local IBM hard disk. But is sure NOT OK
using the Amiga Hard disk.

An other bug I had is also after having used the IBM, again
SOMETIMES, if I go to Shell or CLI the keyboard type characters
like you never seen before. (reverse video, greek like chars etc.)
I try resetting the keymap without success.  I had to reboot again.

Maybe I should've bought an IBM clone...

Vince.

    Before I installed WB 1.3 and FFS, I had no trouble creating and
    using MS-DOS "volumes" as AmigaDOS files in my single hard disk
    partition.  Perhaps the problem is not with the software but with
    the hardware.
        John Sauter

    re .8
    
    I used to be at WB1.2 and had similar problems.  The hard disk
    on the amiga side works without problem.  I tried to relocate
    the IBM file somewhere else (diff cyl) without result.  The IBM works
    great as long as I don't try using the hard drive C:.  
    Can you tell me what kind of hard disk you are using?
    I use a ST-506, 20 meg, 3�" hard disk. Perhaps the problem
    lies there?
    
    The problem is that both program (Janus and Jlink) don't talk
    to each other properly.
    
    Note: I am not using the FFS partition of my Hard Disk, I read
          that Janus/Jlink does not support the feature(?).
    

    Thanks for the comment.
    
        Vince.
     

    I am using a 40MB ST506 drive, with FFS.  I suspect our problems
    are not closely related, because of our very different symptoms.
        John Sauter

    This seemed like the best place to put this, rather than starting a new
    note.  First, the disclaimers:
    
    DISCLAIMER #1:  I do not like MS-DOS.  Unfortunately, though, classes I
    am taking at school require me to use it.
    
    DISCLAIMER #2:  I have searched this notes conference (DIR/TIT=) on the
    following:
    
    Janus, Jlink, Bridge, 2088, IBM, and Hard
    
    and have not found an answer to my question.  (If someone can point me
    to a reference, I will gladly look there.)
    
    CONFIGURATION:
    
    A2000, 2088, 1.3 ROMS with "Fatter" Agnus, 2Mb fast RAM, 20Mb IBM Hardcard 
    (ST506), Hardframe2000 with 45Mb SCSI (ST157N) hard drive.  
    
    The 20Mb IBM Hardcard belongs to a friend who graciously consented to 
    lend it to me along with his A2000; I gave him my A1000 to use until I 
    later upgraded to my present A2000.  I finally managed to get a functional 
    Amiga partition on that drive and so he would like to have it back.
    
    PROBLEM:
    
    I want to get my IBM files off his 20Mb hardcard onto my 45Mb drive. I
    have tried various combinations of commands and have pulled these
    drives in an out of their respective slots trying to accomplish this
    with no success.  I can mount his 20Mb drive as JH0: and use it to boot
    both the Amiga and the PC, although the performance is sometimes
    erratic, with one or more of the processors going out into the weeds
    (unable to get any response; sometimes so bad that even CTRL-ALT-DEL
    or CTRL-A-A won't clear the problem and I have to do a master reset
    with the power switch.)
    
    I have tried to create an IBM virtual drive using JLINK and haven't
    been particularly successful with it.  I would settle for getting this
    to function if it would work consistently.  What I would really like
    to do, though is to set aside an IBM partition on my 45Mb drive that
    I can boot MS-DOS from.
    
    I currently have a small "slow file system" partition to boot from
    (DH0:) and a larger FFS partition for everything else (DH1:).  I have
    also partitioned off a few Mb after DH1: to put IBM files on (this
    partition also uses the "slow file system").  No matter what I do,
    though, I cannot get the PC to recognize the SCSI drive so that I can
    format that partition for MS-DOS.  I have V3.3 of MS-DOS and V2.0 of 
    the Janus software, but no manuals for the 2088, so trying to figure 
    this stuff out has been a real challenge.
    
    QUESTIONS:
    
    1.  How can I get the PC to recognize the 45Mb SCSI drive so that I can
        format the partition for MS-DOS?  If I have the 20Mb hardcard in an
        IBM slot, MS-DOS command FDISK sees that drive only.  If I pull the
        20Mb hardcard and boot MS-DOS from floppy (ugghh!), FDISK claims
        that there are no fixed disks available, although Amiga-DOS sees
        DH0: and DH1: and the empty 3rd partition with no problem.  The IBM
        hardcard is perfectly happy to have two different operating systems
        on it and is capable of booting both of the CPU's -- shouldn't my
        45Mb SCSI drive be able to do the same thing?
    
    2.  If the above is merely a fantasy and cannot be done, does anyone
        have any clues or hints to making JLINK work consistently?  I have
        modified CONFIG.SYS on the PC side to include DEVICE=JDISK.SYS.
        I have tried to fire up PCDisk first and then open the PC window,
        and vice versa with no difference.  I then link the PC virtual
        drive to an Amiga-DOS file that I have previously created on the
        3rd partition.  After establishing the link, I try to COPY files
        from the MS-DOS hardcard to this virtual drive.  After a few files
        on the MFD are copied from C: to D:, the entire system locks up
        to the point were I have to reset by power failing.
    
    3.  Has anyone ever seen the V2 Bridgeboard documentation and would it
        shed any light on the above?  I have had this ordered for months
        and have yet to see it in my hot little hands.  
    
    I have learned a lot of valuable information from this notes file and
    hope that the hardware and software gurus out on EasyNet can give me
    some help.  Thanx.
    
    Dave 

    I'm not near my documentation at the moment, but a few ideas come
    to mind.
    
    1) Yes, The Amiga drive can be made visible to the IBM side, but
    there's a trick to it that I don't recall (perhaps running DPFORMAT
    on the partition, or something concerning the MOUNTLIST entry).
    
    2) I haven't used virtual drive definitions myself; but I remember
    hearing somewhere that the JANUS system had a problem with them
    unless you "filled them up", then "emptied" them just after creating
    them (something to do with allocation).
    
    3) Have you tried the AREAD and AWRITE commands? You could transfer
    files to and from the 2 systems by these commands, even if one side
    is not aware of the proper hardware configuration of the other side.
    

    
    1st.  you should get the book, or like me, a copy of it. 
    is C= still not selling the book?  The new V2 book is
    much better than the rotten V1.  (I used my V1 book at the bottom
    of my cat litter and it didn't deserved it.)
    
    Since I got V2 of Janus,  I have no problem creating/using an
    Amiga HD "partition" for the IBM side.
    
    The secret is that when you are finished using it on the MS-Dos,
    you have to "Unlink" it.  I don't have my docs here but the
    command goes something like: A> Jlink d: /u 
    I kind of remember that you cannot use capital letters...
    
    If you don't use the /u after using it, the file remains at
    0 byte in size and next time you use it, well....
    
    Also you cannot "format" such a virtual disk.  It's size
    is decided at the creation, when you do:
    A> Jlink d: dh0:ibm/ibm.partition /c:number  ; where number is the size 
    						   you want the partition to 
    						   be. i.e.: 10000
    
    What it does, is that it does not assign physical cylinders on the
    HD but rather create a "not amigaDos" readable file. The file will
    grow as the IBM put data in it.  DO NOT create it on the Amiga before
    using it.  PCDisk will take care of that. Make the "number" big enough.
    
    
    N.B.: The actual commands may differ a little, I write this by
          memory.   Let me know if you have problem, I will get
          my book to get the exact ones.
    
     Remember: ALWAYS "UNLINK" when you are trough with it......
               (I know, what a bugger!)
    
    
    As for "file tranfers" :.-1 is right, Aread and AWrite is working
    very good.  The commands are the same as in the V1 book.
    
    
    The reverse is not true, The Amiga needs a physical cylinders on the
    IBM HD.  I cannot comment on it since I never used it.  I use my
    full 30 Meg RLL on the IBM side only.  
    
    P.S.: Make sure the JDISK.SYS you are using on the IBM side is
          from the V2 distribution.   I suspect you are using the
          V1 MSDos distribution.   To check it out, do you have a 
          Amouse.sys on your MSDos disk?
    
    Let me know if you want more details,
    
    
    Vince.

    Thanx for the suggestions.  Unfortunately, I bought my 2088 from a
    dealer who was getting out of the Amiga business, so I got it at a good
    price, but it had no disks or documentation.  The disks were no problem
    since I already had copies of them from using my friend's 2088
    previously.  Everyone I have talked to has said that the highest and
    best use of the V1 bridgecard documentation is as firewood, but it
    would undoubtedly beat nothing all to hell (if nothing else, it would
    at least give me a clue about the syntax!).
      
    I have asked the dealer that I bought my 2000 from to order this for me, 
    but he hasn't received them yet.  Apparently, they are being printed in 
    Hong Kong.  Commodore really seems to be dragging their feet about this 
    "Enhancer" package for the bridgecard.
    
    In the meanwhile, I seem to be having hardware problems, as the Amiga
    clock seems to have gone out to lunch and the 45Mb hard drive refuses
    to warm reboot.  Also, when I open a PC window (MONO) and try to go
    into color mode with MODE CO80, the entire system crashes and comes
    back up with a purple screen.  (I've got the diagnostic color scheme
    printed off somewhere...)  Do you think that this problem could be due
    to the fact that I'm going through an A2300 Genlock?  I have tried all
    of the various combinations of setting the jumpers next to the ribbon
    cable for the 5 1/4 floppy drive.  I have also tried switching the
    video cable for the 1080 monitor back to the video port rather than
    going through the Genlock, but that doesn't seem to make any difference
    either.  Any thoughts on the video display problem?
    
    Dave

    
    Have you tried the following sequence:
    
    1) double click on the "color" icon
       (get a black screen with nothing)
    2) Click on the "screen to back" gadget (Top right corner), go
       back to WB screen.
    3) click on the Mono icon
    4) type mode co80.
    
    If you don't even get a black screen after 1) your problem is
    in the Amiga side of it. (Software or hardware?)
    
    	I had some similar weird bug, after upgrading to V2 of Janus
    because some library were still left as V1 on my HD boot
    partition (DH0:) and I installed it on my SYS: on DH1:.
    I had to double all Janus software by hand (using copy) on
    both, boot partition (DH0:) and ffs's (dh1:).  This got rid of my
    problems.
    
    Make sure the files in Libs/ and Expansion/ are the "same"
    on both your amiga partitions,  that is, of course if
    you are using such partitioning system.
    
    It realy sounds like you have mismatch with your versions.
    (exept for the clock bug, unless your autoexec.bat is trying
    to reference the amiga clock with the routine given in V2.)
    I've never used this routine since my IBM has it's own local
    clock on a multifunction module.
    
    The A2000 seems to have strange clock problem when it crashes
    or hang due to weird unknown causes like yours.   I had 2 oc-
    curences of bizare clock <unset> when trying to reset it. 
    It still remains unexplained.  Haven't any bug for almost a year 
    though.
    
    Good luck again.

    Well, after some sleuthing and applying the Field Service credo (Swap
    'til you drop!), I think I found out what was going on.
    
    I went over to a friend's house and we tried to reproduce the same
    problems on his system.  His 2000 has nothing other than 1.3 ROMs
    and an A2088 Bridgeboard.  I, on the other hand, have 1.3 ROMs, an
    A2300 Genlock, Microbotics HardFrame controller with 45 Mb SCSI drive,
    A2058 Memory expansion with 2 Mb populated, A2088 Bridgeboard and his
    20 Mb ST506 HardCard for the IBM side.
    
    He was able to bring up both mono and color displays on the IBM side
    with no problem, while I could only bring up mono.  We pulled the
    Genlock out of my system and put it in his -- same results; Genlock
    pretty much exonerated.  We switched Bridgeboards.  He was able to
    bring up a color display on MY Bridgeboard (which I had never been able
    to do), while I was STILL unable to bring up a color display on HIS --
    Bridgeboard pretty much exonerated.
    
    During the multiple reboots we went through testing all of this stuff,
    I discovered that something was clobbering my battery backed clock.
    I found this out by typing the SETCLOCK command which appears in the
    Startup-Sequence and it returned the same results I was getting when
    booting the system:
    
    <unset><unset><unset>
    
    We then moved the memory over to my friend's system.  He was finally
    able to bring up a color PC display after much difficulty.  Meanwhile,
    my system now refused to boot from the SCSI drive.  I was able to boot
    the system from DF0:, but it is so agonizingly slow compared to the
    hard drive.  I was finally able to bring up a PC window and get a color
    display at this point, with only a Bridgecard and the SCSI drive.
    
    The bottom line is that the memory board in combination with the SCSI
    drive seem to be causing the 3 problems which I am seeing:
    
    1.  Something is clobbering the clock,
    2.  Inability to bring up PC Color display, and
    3.  Inability to create PC virtual disk without hanging processors.
    
    I also got errors on all 3 partitions of the SCSI drive, so I did a
    low-level format on the drive and re-partitioned it.  At one point,
    I couldn't get the first partition (where I had all of the Workbench
    files) to validate.  After a couple more tries at re-partitioning
    the drive, I got it to validate.  Then, after restoring the information
    I had backed up using QuarterBack a week or so earlier, I could not
    get the SCSI drive to boot the system.
    
    So, at this point, I am going to turn the whole mess back over to my
    dealer and let him figure out (and FIX) what is wrong while I am gone
    for the next 3 weeks.  Thank you all for your input and suggestions.
    
    Dave