| |
Chico
Registered: Feb 2003
Posts: 12 |
StarCommander with WinXP
hi,
can anybody explain me how to use the StarCommander with my
XE1541 cable under WindowsXP? I already have this TweakPackage for the SC, but it will not work. under "DOS" it works fine, but it´s quite inefficient.
cheers
Chico |
|
| |
markus sinalco
Account closed
Registered: Sep 2005
Posts: 112 |
As far as I know, you need a XM1541 or a XA1541 Cable to run SC under running XP.
XE1541 worked fine for me but only in XP Dos Mode on an old 800mhz AMD.. |
| |
Conrad
Registered: Nov 2006
Posts: 847 |
Hi Chico.
I asked a similar question two years ago and the answer I got was that SC isn't compatible with WinXP, because WinXp isn't based on the DOS kernal, disallowing access to parallel/serial ports.
A better one to use is CBM4WIN: http://www.trikaliotis.net/cbm4win download 0.4.0
also get the GUI for cbm4win here: http://sourceforge.net/project/showfiles.php?group_id=122047
Usefull if you're just wanting to insert/extract prg files from real disks, but it won't allow to actually edit a .d64 image as SC does.
EDIT: or what Sinalco said. :) |
| |
Mace
Registered: May 2002
Posts: 1799 |
Otherwise: RTFM ;-)
Which is short for: read the 'readme' in the StarCommander Windows NT/2000/XP tweak package on the page of the current beta release of The Star Commander.
But this same page also says:
WARNING: You should rather make the Commander use the OpenCBM driver from opencbm/cbm4win (0.4.0 or above) to access Commodore drives under Windows NT4/2000/XP/2003; that works much better than using this package! Read the documentation for more information. |
| |
maestro
Registered: Mar 2004
Posts: 727 |
if u want to edit a d64 image use D64Editor
if you cant find this program let me know and ill mail you it or anyone else for that matter...
with this program you can edit a complete d64.....delete files,,extract files,,,add files etc......basically anything you want to do with a d64........
but u cant use it to transferr to and from a 1541......
edit the d64 etc and then use cbm4win with the gui as its much easier |
| |
Chico
Registered: Feb 2003
Posts: 12 |
@Mace: RTFM ...what does the F stand for??? I can´t figure it out ;)
yes, I read the manual, but I can´t start the giveio-driver. it comes along with an error message. and if I really have the wrong cable and Sinalco is right, it can´t work. in the manual stand nothing ´bout what cable I need.
@conrad: ok, thanx for the links, I think I will try this CBM4Win, but I remember I already did in the past and it did not work.
@maestro: I always use the D64-editor, it´s a great tool, but it does not solve my problem.
thanx guys, I will try on...
chico |
| |
Devia
Registered: Oct 2004
Posts: 401 |
Convert your XE1541 cable to an XM1541 cable simply by swapping pins 5 and 6 in the DIN plug |
| |
maestro
Registered: Mar 2004
Posts: 727 |
as devia says you will need to change 2 pins as i needed to do also ill try and find the link to the pictures for you |
| |
maestro
Registered: Mar 2004
Posts: 727 |
i think this is the link
http://sta.c64.org/xm1541c3.html
that is the correct one and not the last one :) |
| |
Chico
Registered: Feb 2003
Posts: 12 |
I ordered a XM cable, maybe I will be able to work with it under WinXP & SC, but at least with the CMB4WIN.
thanx all for your help :)
cheers
chico |
| |
The Shadow
Registered: Oct 2007
Posts: 304 |
Maestro, can you recommend a good d64 editor? |
| |
maestro
Registered: Mar 2004
Posts: 727 |
yes
download d64editor from here
http://almighty.c64.org/d64editor.html
|
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Quote: Convert your XE1541 cable to an XM1541 cable simply by swapping pins 5 and 6 in the DIN plug
isnt it 4 and 6 ? |
| |
maestro
Registered: Mar 2004
Posts: 727 |
no 5 and 6 |
| |
Tim
Account closed
Registered: Mar 2002
Posts: 467 |
Quote: Otherwise: RTFM ;-)
Which is short for: read the 'readme' in the StarCommander Windows NT/2000/XP tweak package on the page of the current beta release of The Star Commander.
But this same page also says:
WARNING: You should rather make the Commander use the OpenCBM driver from opencbm/cbm4win (0.4.0 or above) to access Commodore drives under Windows NT4/2000/XP/2003; that works much better than using this package! Read the documentation for more information.
Has anyone found the mentioned documentation for more information? I've just spent 30 minutes trying to find that refferenced info and failed finding it in various txt's and faq's.
I've got cbm4win with gui working under windows xp with the xa1541 i just built, however i'd love to keep using starcommander, especially since i miss the track/sector counter whilst transferring to .d64.
|
| |
The Shadow
Registered: Oct 2007
Posts: 304 |
I'm having this similar problem. My version of CBM 4 Windows will work with the reset option and my 1541 responds but when I try to get a directory or anything else, the drive does not respond. The status responds with a "driver error". I am a 64 person and new to the PC. How can this be fixed? |
| |
chancer
Registered: Apr 2003
Posts: 346 |
I have the old sort of cable, but use "free dos" on a s*** old machine. that I just use for porting disks. SC works fine with freedos, also..
Wonder if the cable would work under "dosbox" emulation in windows? hhmm
should build a new cable, but haven't had time to as yet.
|
| |
Tim
Account closed
Registered: Mar 2002
Posts: 467 |
Quote: I'm having this similar problem. My version of CBM 4 Windows will work with the reset option and my 1541 responds but when I try to get a directory or anything else, the drive does not respond. The status responds with a "driver error". I am a 64 person and new to the PC. How can this be fixed?
what cable are you using? |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Quote: I'm having this similar problem. My version of CBM 4 Windows will work with the reset option and my 1541 responds but when I try to get a directory or anything else, the drive does not respond. The status responds with a "driver error". I am a 64 person and new to the PC. How can this be fixed?
Shadow, hmmm, check your PAR port mode in the BIOS - try all modes. |
