64hdd problem
- From: "nlcw" <repairs@xxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 17:22:45 +1000
Hi,
I've spent a couple of days trying to get 64hdd (freeware version going)
I've made up an x1541 cable and have played around with 64hdd on 3 different
pc's. They are:
- 486dx4/100 running Windows 98se
- Compaq 486/25 laptop with 8 meg ram running Windows 95
- Amd 5x86/133 (Pentium 75 equivalent) running Windows 95/Windows 98
I've loaded in Dos mode on all machines and ran 64hdd with different command
line options, and even played around with memory managers like: emm386 etc
with no luck (still have to try Qemm386 as mentioned in 64hdd docs to help
get it going)
I ran xcdetect to check my cable and its seems to pickup device 8: when I
connect a 1541-II drive to the IBM,
but when I try and let my sx-64 access the IBM to use as a hard drive, 64hdd
seems to say everything is fine but says: x1541 not auto detected.
When I startup the IBM my sx-64 resets itself (telling me the cable should
be working as I think this is normal to happen)
64hdd just sits there idling with a list of devices activated and not
activated e.g.
I used the following command line to attach a file from a folder on the IBM
to device 9: (so my sx-64 can access the .d64 file on the IBM and treat it
like a floppy disk)
64hdd -<code> +9 c:\64hdd\demofile\ducks.d64
I even played around with the +p speed option with no luck. I noticed
aswell that 64hdd beeps 2 or sometimes 3 times on the IBM when I try and
access the .d64 file on the IBM. What do these beep sounds mean? as I cant
see it mentioned in 64hdd's docs.
Maybe I should try running 64hdd under Dos 6.0+ or something...
Any help appreciated...
Thanks,
nlcw.
.
- Follow-Ups:
- Re: 64hdd problem
- From: WhiteWolf
- Re: 64hdd problem
- Prev by Date: Re: Commodores original 16 bit?
- Next by Date: Re: Using a GEOS64 V1.3 upgrade with GEOS128
- Previous by thread: Commodores original 16 bit?
- Next by thread: Re: 64hdd problem
- Index(es):
Relevant Pages
|
