#New Janus Software
39 messages in this thread
My dealer gave me a copy of the new Janus software and I tried to install
it last night. All went well, except that I can't get the utilities
(Awrite, Aread and Atime) to work. I am using the old XT Bridgeboard and
aside from the periodic "can't find libraries" problem, all worked well.
When I install the Commodore deinterlacer card and bought a multiscan
monitor a while back I was not getting the greatest of screens on the DOS
side. But, it worked and what I really need is the aread feature to
transfer WP files to WP5.1. The new screens are great on the multiscan.
I ran the AMIGA Janus install program and copied all the new Janus PC
files to the Janus directory on the DOS HD. (Yes, I deleted all the old
Janus PC files before copying in the new ones). When I give the Awrite
command, the HD starts running, but the system hangs. Same thing with
Atime. I tried configuring the memory at A….., as well as the other
options. One big problem is that the read file on the disk indicates that
the software is appropriate for all versions of the Bridgeboard, manual I
had was specfic for the FX board and had not specific instructions on
setting up the software for the other hardware.
The read files recommends deactivating caching if one is using 68030 board
and I tried that, with no success.
I recall Betty commenting a while back she was having trouble with
Aread/Awrite and wonder if that is a bug in the latest software, or if I'm
doing something wrong.
Any help would be appreciated.
Bill, I don't have the new Janus software. My problems were with the
older version.
—Betty
Betty:
Thanks. Maybe someone else can come up with an answer.
Bill,
Everyone was saying they were having problems with AREAD and AWRITE
under 2.04 and using 2.1 Janus…yet I had no problems. Well, as it turns
out, I had no problems because I didn't use AREAD or AWRITE that much.
Recently I had a bunch of files to copy from 5.25" to 3.5" disks, and tried
to use AWRITE to do it (using the Amiga's 3.5" drive as PC0: under 2.1).
Darn if I didn't start to have problems wtih AREAD and AWRITE. I'd get a
Janus Handler not Found message the first time I tried to use it about 90%
of the time. IF I tried to use it after that…it'd lock the BB.
Well…I found a work-around, that so far, after lots of testing by
me has worked 100% every time, not matter if I use AREAD or AWRITE nor
which Amiga device I read/write to/from:
I created a script file on the Amiga that is two lines long:
PCRESET
BINDDRIVERS
I run this anytime after the first time I boot up the BB but before
using AREAD or AWRITE. So far, it's worked every time.
There's a few things you need to be aware of though:
1. If you've moved your SYS: partition since startup, you have to
make sure there is a directory SYS:Expansion and in that directory are the
two janus files (janus.library and janus.library.info).
2. Also, this command will obviously reset your BB, so make sure
it's idle and all open files are closed when you issue the command on the
Amiga side.
3. I've only run this after I open up the PCWindow, I don't know if
that makes a difference or not, but you might try it and see if it works
for you.
Don
Don:
I'll try it and see if it works.
Bill
Don:
Eureka!! It works perfectly. Even ATime works.
Now the question. Why? How did you figure it out and what is the bug
you get around?
By the way, I am using the XT BB and as I recall so are you. Were you able
to use the software to make df0: the A; drive on the DOS side? I didn't
think that would work since the documentation I was reading talked about
setting jumbers on the new board to pull off that trick.
Bill
Bill,
Yes, I have an XT BB. No, you can't use Flipper on the XT BB.
How'd I figure it out….it kept telling me that it couldn't find
the Janus Handler, yet the bootup show'ed it found the Janus handler when
the BB booted so I figured it lost it somewhere along the way. Also, I
noticed if you did a pcreset while you watched the MS-DOS screen a lot of
the time it would not find the Janus handler on the reboot. So I just
wondered what'd happen if I re-ran BindDrivers…and it all started to work
just fine.
I tried moving BindDrivers around in my startup, or even waiting
until the startup was done and I was at a CLI prompt before I issued it by
hand…as you apparenly also found…it didn't seem to make any difference.
But the reboot and reload script seems to always work…so I stick with
what works <grin>.
Anyway…I'm glad it works for you too. At least that tells me my
system isn't as weird as I though…they're apparently all a bit weird
<grin>.
Don
Don…
I like your solution…can I print it in CROSSINGS? It's much better (and
more reliable) than just rebooting the PC
Marion
CROSSINGS
Newsletter for the Bridgeboard, etc.
Marion,
Yes…you have my permission to reprint it as long as you note the
information was found in the Amiga User Forum on CompuServe and credit me
as the source of the information.
Don
Don,
What I can't understand is that if this bug is common, why hasn't
Commodore fixed yet? It seems that others are having problems with the
software.
Nonetheless: "Very clever Sherlock Holmes.":>)
Bill
Bill,
I can't speak for Commodore, thus can't say why it hasn't been
fixed or if the program development team is aware of it. I know that Greg
got my message and he'll pass it on…but he also states he has no such
problem.
Don
Don:
Well thanks with the help. As always, I am grateful.
Bill
This may be the answer to my question, too. I'll try it (with crossed
fingers). BTW, you should pass this info on to CBM. I spent about an
hour (see my message) with a chap there who could not figure out what the
problem was.
(Thought it might be something to do w/BINDDRIVERS and I inserted a couple
of extra ones in my startup sequence and moved them around a bit, but gave
up when it didn't seem to work.)
Later: It works! IT WORKS! Fantastic! Thank you very much – and God
Bless CIS. I'll pass this on to my dealer and his technicians tomorrow.
I'm sure they'll be happy to have this news. (I hooked my little script
file up to a duplicate of the PCReset Icon and placed it in the bottom of
the window, so I can click it as soon as the window opens.)
…..Nancy
Much happier tonight in Edmonton
Nancy,
Glad you're happier. Hopefully, CBM saw this thread, but just in
case, I'll point Greg to it.
Don
Don, I have 2.1 and have had no problem with the utilities.
Ron
Ron,
It seems to be spotty when and if the utilities will work. As I
said, I didn't think I had the problem either….until I started using them
more often and the problem cropped up about 90% of the time. With the
workaround, it never crops up anymore.
I tried the "official" tricks even though I've only got a 68020 in
my 2500 and it doesn't cache data, only instructions, so it shouldn't have
needed those tricks in any case….but they didn't work.
It may have to do with the BB ROM level, I've still got the
original XT-BB ROM on my BB. It may have to do with the motherboard level,
mine is a very early 2000 motherboard with only the capacitor removal
modification done to prevent the first keystroke missing problem.
Or it may have to do with the phase of the moon <grin>.
Don
I still have (knocking on wood) a 4.2 rev mother board, but I have the 3.61
bios (which was far better behaved) that came out a couple of years ago. I
was a 'semi' beta tester of 2.1 so I've been using these utilities for
quite a while now.
Ron
Don..
That's interesting…I have an older motherboard too.
This thing with the utilities not working is probably the most common phone
call I get. Now that I think about it, it may be that they're all 2000s.
But I'm not sure.
I like the phase of the moon theory!
Marion
CROSSINGS
Newsletter for the Bridgeboard, etc.
Don,
Another note. The same problem came up with my A2286, got worse when I put
in an ATOP accelerator, and continued with the A2386. I never saw it with
the XT BB, because I upgraded to the 2286 at the same time as I upgraded to
WB 2.04.
Marion
CROSSINGS
Newsletter for the Bridgeboard, etc.
Marion,
Ok, that rules out the BB's ROM since the newer BB's have newer
ROMs on them yet I have the original 3.4 ROM on my BB.
Don
Don,
I also had some problems with AREAD and found that if you turn both
caches off (if you have an 020/030/040) or run the new Enforcer before
running Binddrivers that my problems seemed to have disappeared. However,
when I was only disabling the inst cache the AREAD problems would appear. I
now boot with both caches enabled, but run the new Enforcer prior to doing
Binddrivers and leave Enforcer on as long as the BB is in use. This has
eliminated the need to disable the caches, since the new Enforcer doesn't
seem to mind that the MMU is in use otherwise. I don't know if this
relates to your problem or not, but thought I'd pass it along.
Steve,
yup…I tried it with the new enforcer…didn't seem to make much
difference.
Judging by the varied repsonses…I suspect it has something to do
with the ROM rev on the BB itself.
Don
There is a thread in the BB section which addresses this problem which
other users have also had. Don Curtis, the sysop (76703,4321), provided
the answer. After opening the window, run the following script:
PCRESET
BINDDRIVERS
This will take care of your problem. (I just attached the script to a copy
of the PCRESET icon, using IconX, and placed it in a handy spot in the
window.)
Hi.
What are your exact configurations, when those Problems occur.
I'm just wondering, because my Amiga 2000 (OS 2.04 resp. 2.1) with a A2286
Bridgeboard and Janus 2.1 causes NO Problems at all when using AREAD or
AWRITE in the correct way.
The only thing is, when I AREAD a MS-DOS binary file and try to run it or
to unpack it (*.lzh files), the ENTIRE system breaks down, if i forgot the
"/b" with the AREAD command.
Normally, if something breaks down, it should ONLY be the A2286 Subsystem,
but NOT the AMIGA main system.
But since this is a avoidable problem, it doesn't cause me many
difficulties…. It's just another big questionmark to Commodore's
Janus-Software. Like that one, that the Bridgeboard Installing Software did
not support the OS2 Software, and I could only install my system using
procedures, an unexperienced user would never think of or even understand
them. This can't be the right way, to establish an "Easy to use"-Image for
the Amiga.
CU Sven Witter
Sven,
My exact conditions are random. The point being that AREAD and
AWRITE aren't reliable unless I pull the reboot/rebind trick. It works
flawlessly then. It's some quirk between an old A2000 (now an A2500/20), an
old BB, the new chipset and the new OS.
While you're right…you shouldn't have to do it…for many it
seems it's the only thing that works.
Don
Don,
Just FYI, it's not just old BBs–it also happens on new 386s. It seems more
and more likely that it has to do with old motherboards.
Marion
CROSSINGS
Marion,
I missed the first of this thread. What problems are people who have
older motherboards having with BB's. I have a 486SLC on the way (EMC's)
and have a 4.3 (or is it a 4.3) motherboard.
Thanks…
Michael,
There's a problem getting AREAD and AWRITE to work consistently.
But there's a work around. Once the Amiga is booted, you reset the BB
(using the PCRESET command) and immediately do a binddrivers (even though
you have already done one).
I have that in a 2 line script file:
PCRESET
BINDDRIVERS
That I envoke when I want to use AREAD and AWRITE for the first
time. Once that's done…until you turn your machine off…they'll work
just fine without having to do it again.
Don
Don,
What are AREAD and AWRITE? Not owning a BB yet, I do not know? Are they
the programs that allow you to use the Amiga floppies as IBM floppies?
Thanks…
AREAD & AWRITE are utilities that allow you to move files between the
Amiga side and the PC side, via the dual port ram.
I see. Yes very useful. If I have a problem, I will try the workarround
suggested..
Michael,
AREAD and AWRITE are the programs that allow you to transfer files
from the Amiga side to the BB side…and vice versa. They are MS-DOS
programs that come with the BridgeBoard software.
Don
Don,
I need some advice on installing an auto-booting virtual Hard Disk
for the XT-BB. I recently purchased a GVP Series II 8+HC and tried to run
the BBinstall program that was included only to find that it called for
the Amiga DOS 1.3 PCInstall disk which unfortunately for me was completely
covered with read-write errors. I purchased the latest version of the
Janus software for $35 from a mail order company which seemed reputable
and promply received two disks without any manuals or documentation.
After calling the company twice I recieved a photo copied version of the
Addendum to the A2286/A2088 User's Guide which forbids photocoping on the
first paragraph of the first page. I was royally pissed.
After messing around with the Install program on the AmigaJanus disk I
have been able to reactivate BB, create a virtual Drive file named DriveC
in a Partition named IBM:, installed all the files, and edited all the
User-Startup lines that I can think of. Only one problem. The XT-BB
still does not recognize that there is a hard drive with partitions and a
virtual drive file for it to access. Some how I have the sneaking
suspicion that I'm missing something from my Janus upgrade package, and
that Commodore isn't going to help me until I spend more money to buy what
I already have from a legit establishment.
Can you give me a list of what I need to do and have to get this BB
running with a GVP HC, JANUS 2.1, and AmigaDOS2.04.
Desperately,
Kapryan Kennedy
Kapryan,
You need to make sure you've done the following:
1. Created your virtual drive via the MAKEAB command.
2. Make sure the filename you used above is in the file
sys:pc/system/aboot.ctrl
3. Reboot the bridgeboard (or whole machine for that fact) from na
MS-DOS floppy.
4. Use FDISK to 'activate' the C: drive
5. FDISK will cause a re-boot of the BB, again…boot from a floppy
6. FORMAT the C: drive and make sure you use the /S switch that
will cause it to be bootable.
Don
Michael,
Looks as if you got the answers you need already. BTW, it's not just the
AREAD and AWRITE that have this problem, it's also the programs that allow
you to use part of your Amiga drive as a drive for the PC. In other words,
anything that involves transferring data back and forth between the two
sides. The "older motherboard" theory is something I'm checking ut. But
Don's workaround seems to solve the problem, anyway.
Marion
CROSSINGS
Newsletter for Amiga/PC compatibility
Sven,
May I ask how old your system is? It's beginning to look as if these
problems only occur with older motherboards. Also, there may be differences
in the Amigas sold in Europe.
I agree with you that the installation problems shouldn't happen, but I
think Commodore expected to have the 386 BBs (with the new Janus software)
released before WB2.04. I don't think the combination was beta-tested
properly.
Marion
CROSSINGS
Newsletter for Amiga/PC compatibility
The XT Bridgboard has default settings at E000.
The 286/386 BB have default settings at D000.
Configuring at A000 turns off the Janus utilities as far as I can tell.
John G. Ata
Sterling, VA
John:
I tried all the defaults available and one worked. The fact is that I
didn't remember the E000 setting for the XT BB and I will try it when I
tryout a workaround suggested by Don Curtis.
Bill