dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Mar 30, 2010 10:42:14 GMT -5
|
|
|
Post by relayer on Mar 31, 2010 7:07:56 GMT -5
Is your printer port in the appropriate mode (EPP, etc.). That should be mentioned in the Star Commander instructions.
I haven't used my X1541 on any modern system. Mine is currently working on a 10 year old Compaq laptop which runs Windows ME. I don't use it often, but it does work well from a DOS shell.
If you are using a modern system, I wonder if the operating system is interfering with the use of the parallel port by Star Commander?
|
|
dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Mar 31, 2010 12:34:22 GMT -5
Is your printer port in the appropriate mode (EPP, etc.). That should be mentioned in the Star Commander instructions. I haven't used my X1541 on any modern system. Mine is currently working on a 10 year old Compaq laptop which runs Windows ME. I don't use it often, but it does work well from a DOS shell. If you are using a modern system, I wonder if the operating system is interfering with the use of the parallel port by Star Commander? WHAHOO!! Star Comander is runing the drive just fine NOW! I have an old 486 DX2 100 megahertz Gateway board running Win95 . I did have to turn on ECP. and get the transfers settup for the XM1541 cable (i just have the printer port adapter)--slick-- plugs into the LPT port and the standard CBM Drive cable into the drive and the adapter. :-) I think reading the Star Commander doc paid off real well. Used Warp!to get it working. Now, I guess it's time to play. Thanks for the Help, dilbert
|
|
dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Apr 4, 2010 21:19:26 GMT -5
As I ran off to test the now working adapter and 1541 drive I wondered if things would run smoother? Well, they did for awhile. Put in a old c=64 disk labeled "Assembler". The 1541 did its part . I had 16 programs listed. found the COPY key (f5) quickly filled the new C:\c\D64 with old .prg files. Then what did I do with my stash of "new" ;-) 5 1/4 floppys? Oh yes. Over here tucked on the bottom shelf. Drag out the partial box of those nice color heavy duty TDKs for the occasion. Put a nice new BLUE TDK into the drive. Drive hammers --not formated... find Star Commanders Format drive key right? NOPE! Wait, I can just walk over the real one and format it there! I can but sorta lame way to do it. sooo after awhile at that I finally gets her done. Back to the Star Commander PC and 1541 and copy back the files to the new blue tdk disk. Pull it out and troop back to the real C=64. Pop the blue baby in and see if t will run? lists ok. run the "DOS WEDGE64" wait is just says "DOS WEDG" ? and "DOS 5.1" says "DOS 5_1-.PRG neither will run. one runs the other and the names are Wrong. So even if i use the "wedg" it will be looking for the real"DOS 5.1" <grr> WELL, I should be makeing a .D64 image let me try that . Oh yes, Right click to high lite the selected files. Next its shift-f1 if you've also ready on the PC C:\ side....... I think......... I've really started to wonder....if ...I'll....ever.... learn...it at.......... slugo.proboards.com/index.cgi?action=display&board=general&thread=706
|
|
dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Apr 20, 2010 17:08:57 GMT -5
As I ran off to test the now working adapter and 1541 drive I wondered if things would run smoother? I started to wonder....if ...I'll....ever.... learn...it at..........all. I've now let it sit for a few days. Regained my drive to try it again. Plan? Maybe... I tried a newer machine 64 meg of ram and Win 2000 Pro. Docs said to use the WinNT driver & installer program with the USERport test program. But as of last night, all I could do was play the catchy little tune though the speakers.. and "DRIVE 8 not found". What to do? ANY BODY KNOW?
|
|
|
Post by relayer on Apr 21, 2010 9:49:22 GMT -5
Pop the blue baby in and see if t will run? lists ok. run the "DOS WEDGE64" wait is just says "DOS WEDG" ? and "DOS 5.1" says "DOS 5_1-.PRG neither will run. one runs the other and the names are Wrong. So even if i use the "wedg" it will be looking for the real"DOS 5.1" Those filenames seem too 8.3'ish to me, like they were copied with the DOS filename size restrictions in effect. I'm wondering if there are other modifications of data going on in the transfer. Even if the filename is wrong, as long at the C= application on the disk doesn't need additional files to work, the filename should not matter.
|
|
dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Apr 24, 2010 18:29:12 GMT -5
Pop the blue baby in and see if t will run? lists ok. run the "DOS WEDGE64" wait is just says "DOS WEDG" ? and "DOS 5.1" says "DOS 5_1-.PRG neither will run. one runs the other and the names are Wrong. So even if i use the "wedg" it will be looking for the real"DOS 5.1" Those filenames seem too 8.3'ish to me, like they were copied with the DOS filename size restrictions in effect. I'm wondering if there are other modifications of data going on in the transfer. Even if the filename is wrong, as long at the C= application on the disk doesn't need additional files to work, the filename should not matter. Yes, going from c64 to windows they get clobbered! Must need to set something else in Star Commander. There was something in the manual that said if you save them into a zip (compacted) they would keep their normal filenames. and we do this all for FUN!
|
|
|
Post by relayer on Apr 27, 2010 6:32:13 GMT -5
and we do this all for FUN! I'm sure there is medication out there to help all of us who try it... ;D Be glad you aren't transferring PC to/from Amiga disks (for free). The best solution I could come up with, for whole floppies, is mount a SCSI CD-ROM drive in the Amiga, burn a bunch of .adf files onto a CD (with a 31 character filename limit), and use adf2disk on the Amiga to create a native floppy. Individual files can be moved the same way. The "simple" alternative would be a null modem cable, terminal programs, and zmodem.
|
|
dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Apr 27, 2010 20:22:58 GMT -5
and we do this all for FUN! I'm sure there is medication out there to help all of us who try it... ;D Be glad you aren't transferring PC to/from Amiga disks (for free). The best solution I could come up with, for whole floppies, is mount a SCSI CD-ROM drive in the Amiga, burn a bunch of .adf files onto a CD (with a 31 character filename limit), and use adf2disk on the Amiga to create a native floppy. Individual files can be moved the same way. The "simple" alternative would be a null modem cable, terminal programs, and zmodem. Hey a fellow traveler! read your blog www.vintagevolts.com/index.php?option=com_content&task=blogsection&id=5&Itemid=28While I'm here... thanks Rob for info on this topic. #109 podcast.robohara.com/
|
|
|
Post by relayer on Apr 28, 2010 7:30:19 GMT -5
I still work on that Amiga from time to time. I'm trying to get past hardware limits of hard drive sizes. I have a few 18GB drives which my GVP card only see as 400MB or 900MB for whatever reason. One of these days, I'll find a solution. Then I can move on to whatever other classic PC I want to revive. Maybe the TRS-80 Model 4 would be next.
|
|
dilbert
Full Member
Registered Linux User #306113
Posts: 223
|
Post by dilbert on Apr 28, 2010 10:16:52 GMT -5
I still work on that Amiga from time to time. I'm trying to get past hardware limits of hard drive sizes. I have a few 18GB drives which my GVP card only see as 400MB or 900MB for whatever reason. One of these days, I'll find a solution. Then I can move on to whatever other classic PC I want to revive. Maybe the TRS-80 Model 4 would be next. Suggestion: 18GB, large drive needs large drive formating....something to check on. There is a question that FDISK asks prior to doing the low level stuff , if I remember right. (this is my view from the PC-side of things) ;-) your card{and I DON"T know !} could be fine, (guess)if you get the disk formated right. (PC-side& Linux view) Disclaimer: I have never even touched an Amiga! ;D ;D ;D I'm working with 2 C=64's & 2 C+128's plus junk or near junk PCs back to STAR Commander:::> It is running on WIN95 and working fine with the 1541!! (read--hardware&software are working together on the startup level) Prior to the operator doing any thing. Thats good! so I'm going to work with that and ASSUME that I need to do some more READING in the manual and the online help.
|
|
|
Post by robertb on Apr 28, 2010 20:25:39 GMT -5
I still work on that Amiga from time to time. I'm trying to get past hardware limits of hard drive sizes. I have a few 18GB drives which my GVP card only see as 400MB or 900MB for whatever reason. Are you using Amiga OS 3.5 or 3.9? Those may solve your hard drive limitations. Back in L.A. during the weekend, Robert Bernardo Fresno Commodore User Group videocam.net.au/fcugJuly 24-25 Commodore Vegas Expo 2010 - www.commodore.ca/forumand click on ComVEX
|
|
|
Post by relayer on Apr 29, 2010 8:42:59 GMT -5
Are you using Amiga OS 3.5 or 3.9? Those may solve your hard drive limitations. OS 2.1 I wanted to maintain compatibility with all the software I've acquired over the years. I do have several 9GB and 18GB drives to play around with. I may try a fresh OS 3.0+ install, just to see how things work. I'm afraid my hardware might be a limitation. FaaastPREP and HDToolbox detect the proper number of cylinders and heads for those drives, but only offer <1GB total size. I didn't explore block size overrides yet using advanced settings. Maybe I should consider low level formatting the drives. Wouldn't hurt. I tried to burn a GVP 4.15 ROM for my GVP Impact Series II , hoping that will fix the issue, but I haven't had luck getting it to work. It currently has the 3.12 ROM. I burned a duplicate of the 3.12 ROM and the duplicate doesn't work, either, even after verifying the burn image. There might be a compatibility issue with the EPROMs I'm using (mostly pulled from old boards).
|
|
|
Post by relayer on Apr 29, 2010 16:20:08 GMT -5
I think I solved my space issue.
I finished partitioning a 9.1GB Fujitsu SCSI III drive (using a SCSI adapter board). I wasn't familiar with any partition limits, so I made near 1GB partitions... ALL 11 of them, FDH0:-FDH10:
Having originally four named volumes, I now have the following volume names (icons) on the screen at all times:
Main Main_Not!!! Stuff Toaster Storage_1 Storage_2 Storage_3 Storage_4 Storage_5 Storage_6 Storage_7
The "Main_Not!!!" volume is an old joke, nearly two decades ago when I only had two partitions, Main and whatever was not 'Main'.
They all seemed to have quick-formatted correctly and I'm in the process of transferring the other SCSI drive's contents to the new one. So far, so good. I can only imagine how much Chip RAM is being used by all the drive icons.
|
|
|
Post by relayer on Apr 30, 2010 8:01:58 GMT -5
|
|