8bitfiles.net/archives

home *** CD-ROM | disk | FTP | other *** search

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / JIFFYDOSMSGS.ARC / 00JIFFYDOS next >

Wrap

Text File | 2019-04-13 | 33.5 KB | 900 lines

************ Topic 6 Thu Oct 24, 1991 C128.JBEE [* Sysop *] at 04:50 EDT Sub: JiffyDos A place to post questions, answers, comments, and suggestions for JiffyDos, the disk speed up system from CMD that started it all! 111 message(s) total. ************ ------------ Category 12, Topic 6 Message 1 Mon Oct 28, 1991 J.ROBBINS16 [JBUS] at 21:33 EST Hi again:) I've been wondering if adding JIFFYDOS to my 1541 and 1571 Drives would interfer in anyway with my RamDrive and RamLink or using GateWay64/128? ------------ Category 12, Topic 6 Message 2 Tue Oct 29, 1991 HOWIE-CBM [H.HERMAN1] at 04:07 EST JBUS, Other than the speeding up of drive read/writes, I cannot think of any thing else that would be noticed. Howie ------------ Category 12, Topic 6 Message 3 Tue Oct 29, 1991 C128.JBEE [* Sysop *] at 06:05 EST There are only two things that will be effected by adding JiffyDos to a 1571 Lynx (won't run on a JiffyDos 1571 - I don't know why) some EGA and older Eypx games (i think because they keep the sprites active while accessing the disk). The problem with the games you can fix by turning off JD, the Lynx problem can only be solved by not using it. Anything that would dislike JD most certainly would dislike your REU or Ramdrive (example: VMAX!) Other than that I can't think of any problems except a good to great gain in speedup of your reads and writes. Note: if you have the older rom in a 1571 the JD upgrade contains the new one! ------------ Category 12, Topic 6 Message 4 Tue Oct 29, 1991 J.ROBBINS16 [JBUS] at 20:27 EST Thanks guys:) I really hate "VMAX" with a passion, it screws with just about anything alive, but I got Maverick to kill VMAX and its' little bummp bummp on the drives. (really hate that bumping most of all) Anyway, so far nothing but good news about Jiffydos for the drives (except the 1571) so I'll get it for the 1541's (they're tooooo slow) ------------ Category 12, Topic 6 Message 5 Sat Nov 30, 1991 MC.LEWIS [MaryL] at 09:58 CST I just got version 5 of Maverick and can't get any of the programs to boot? Are there any known problems of this with JiffyDos? When I try to boot, my 1571 makes a lot of "thuds", then nothing happens. I have no problems with any other software and have recently had my drive checked out o.k. I tried turning off JiffyDos and still no success. I'm going to check it out on a friend's non- JD system and see if the disks are bad, but I thought I would see if there are any known problems - Thanks. ------------ Category 12, Topic 6 Message 6 Sat Nov 30, 1991 CMD-DOUG at 15:09 EST I use Maverick v5 from time to time with JD without problems. I don't know of any incompatibility between the two. ------------ Category 12, Topic 6 Message 7 Sat Dec 07, 1991 PAUL-MB at 15:53 CST Simple question. If I get the 128D version of JiffyDOS, will I need 2 extra ROMs for each of my external drives? In other words, a ROM for each drive? \/\/\/ Paul /\/\/\ [Was D.MCALEER1] ------------ Category 12, Topic 6 Message 8 Sat Dec 07, 1991 C128.JBEE [* Sysop *] at 21:27 EST If you get JiffyDos for your C128D and have external drives you will need additional JiffyDos roms to take advantage of the speedup in each individual drive. Though you still can use JiffyDos with drives that do not have JiffyDos roms. You just will not see any disk speedups in those drives. ------------ Category 12, Topic 6 Message 9 Tue Dec 10, 1991 PAUL-MB at 18:40 CST Thanks, JBEE, I needed that. :) \/\/\/ Paul /\/\/\ ------------ Category 12, Topic 6 Message 10 Tue Dec 10, 1991 C128.JBEE [* Sysop *] at 23:47 EST You're welcome :) ------------ Category 12, Topic 6 Message 11 Thu Mar 26, 1992 CAPT.CARL at 07:45 EST Greetings. I was just wondering if anyone has reported or experienced any problems while downloading files from online services while JiffyDOS was enabled. I am finding some corrupt files which I never had prior to installing JiffyDOS. My problem may have nothing to do with JiffyDOS, but thought I'd ask, might help me find the problem by eliminatingwhat it COULDN'T be. Thanks in advance! --- Carl ------------ Category 12, Topic 6 Message 12 Fri Mar 27, 1992 HOWIE-CBM at 04:38 EST Carl, You didn't say what Term you are using while experiencing this prob, or what is happening to the bad files. JD doesn't affect files that I've downloaded with the several Terms that I use. One thing to watch for is a Term that does not strip X-mo padding. Some programs will not run because of this. BTP is one that does not strip X-mo. However, using its buffer, lets you do this quite easilly later. Dialogue128 will strip padding, so this never shows up as a problem. Howie ------------ Category 12, Topic 6 Message 13 Fri Mar 27, 1992 C128.JBEE [* Sysop *] at 13:26 EST I know you probably aren't using a fastload cartridge but using one of these while downloading can corrupt data depending on the cartridge. ------------ Category 12, Topic 6 Message 14 Mon Mar 30, 1992 CAPT.CARL at 04:12 EST Ahh, thanks for the info... I think I got the answer I was looking for and the problem is NOT the JiffyDOS. I've had problems using Wizard term here (C-64) and also with some filesI d-loaded from Q-Link. Most of the bad files are GEOS files, so I'll look at my GEOS conversion program next for the problem. Thanks again. --- Carl ------------ Category 12, Topic 6 Message 15 Mon Mar 30, 1992 PAUL-MB at 19:32 EST This is just a minor thing, but I thought I'd post it here since it seems to be the JiffyDOS - not my RAMDrive - talking back. I've found that if you try a DOS command (regular @...) from some 128 windows, your command is scrolled off the window and the computer locks up. A R/S-RESTORE is needed to get back the prompt. This only happens with small windows. Odd! ~~~ Paul ~~~ ------------ Category 12, Topic 6 Message 16 Fri Apr 10, 1992 C.GAMLOWSKI1 [Gamlowski] at 04:12 EDT I have an older version of Jiffy DOS (I think it's 5.0 or 4.0, not sure). How do I upgrade to the latest version? I do have a receipt. Thank you, Paul ------------ Category 12, Topic 6 Message 17 Fri Apr 10, 1992 C128.JBEE [* Sysop *] at 08:23 EDT You call CMD (1-800-638-3263) tell them you want to trade in the old version. They give you a Return Material Authorization number (RMA) and you return the old rom set and get a new rom set. I believe the price is around $25-$30 plus S&H. ------------ Category 12, Topic 6 Message 18 Fri Apr 10, 1992 C.GAMLOWSKI1 [Gamlowski] at 21:54 EDT Thanks Sysop! What are the major new features of 6.0 (or what is the latest version), compared to say 5.0? Any advantages for a C-128 owner? Paul ------------ Category 12, Topic 6 Message 19 Sat Apr 11, 1992 C128.JBEE [* Sysop *] at 10:55 EDT The biggest difference I could see were the F-keys were redone a bit nicer. I know they probably redid a lot of little things but I would not be able to say what they are. As for any advantage to upgrading the roms, I do not know. How I would see it is if I am happy with v5.0 why upgrade for the sake of upgrading. If you are thinking about buying something like a Ramlink I would not upgrade the roms at all because it comes with JD built in. Also, $30 would be close to the price of a Swiftlink or SID Symphony stereo cartridge. I think for $10 extra dollars you would get a lot more mileage out of your money with something like SID Symphony that would let you listen to all the awsome stereo sids online. Not to mention quite a few commercial programs now support stereo sids. Or if you were a big Geos user I would think about Perfect Print instead. ------------ Category 12, Topic 6 Message 21 Fri Apr 24, 1992 CMD-DOUG at 22:04 EDT Version before v6.xx did not have several of the currently present features, like the file copier and interleave factor settings. I think there were other changes, but it has been SO long since I saw a version 5 that I really can't recall all the changes anymore. The upgrade policy, last I heard, was scheduled to be discontinued, and that may have gone into effect by now. Version 6 has, after all, been around for about 3 years now. ------------ Category 12, Topic 6 Message 22 Wed Jun 10, 1992 M.MCCORMIC10 [Mike Mc-] at 05:25 EDT Now that I have RL all I need is the ROM for JD,right??Do they come with instructions?? Mike Mc- ------------ Category 12, Topic 6 Message 23 Wed Jun 10, 1992 C128.JBEE [* Sysop *] at 08:47 EDT Ramlink has JiffyDos build in! All you should need is additional roms for whatever drives you use. ------------ Category 12, Topic 6 Message 24 Fri Jun 12, 1992 CMD-DOUG at 00:26 EDT JBEE is correct, though I think that maybe that is what Mike meant to ask. And yes, every JiffyDOS ROM comes with full installation instructions. ------------ Category 12, Topic 6 Message 25 Tue Jun 23, 1992 M.MCCORMIC10 [Mike Mc-] at 05:55 EDT I accidently hit he f1 key the other day and I got they disc directory.I tried a few other commands and they seem to work. Could I have JD in my system?I have a RL but I never upgraded my FSD-2 disc drive. Mike Mc- ------------ Category 12, Topic 6 Message 26 Tue Jun 23, 1992 CMD-DOUG at 08:49 EDT RAMLink provides you with all of the JiffyDOS commands and DOS wedge. If your disk drives do not have JiffyDOS ROMs, you simply will not get any increased speed for disk access. Also, the company which produced the FSD drives did at one time have a contract with us to provide JiffyDOS drive ROMs in their drives, so you might be getting the added speed on that drive. ------------ Category 12, Topic 6 Message 27 Tue Jun 23, 1992 HOWIE-CBM at 09:27 EDT Mike, With RAMLink enabled, your operating system has *most* of the JiffyDos commands operable. However, if a drive does not have JiffyDos, no speed enhancement is possible. Howie ------------ Category 12, Topic 6 Message 28 Wed Jun 24, 1992 M.MCCORMIC10 [Mike Mc-] at 05:54 EDT Thanks guys- Are there any measurements that I can use to judge the speed of the drive? Mike Mc- ------------ Category 12, Topic 6 Message 29 Wed Jun 24, 1992 CMD-DOUG at 08:19 EDT The easy way is just to send it a "UJ" command then read the error channel. If it has JiffyDOS, you'll get a JiffyDOS message. The other way to check is to find a long PRG file. LOAD it with your RL enabled, making sure that you time the load. Then reboot with your RL disabled and LOAD the same PRG file, again taking note of how long it takes. If it has a JD ROM, you'll see quite a bit of difference. ------------ Category 12, Topic 6 Message 30 Wed Jun 24, 1992 HOWIE-CBM at 08:38 EDT Mike, I have a short routine (it is here somewhere) that will tell you how fast a drive is spinning. In fact, it will tell you how fast anything is spinning. Is this what you might be referring to? Howie ------------ Category 12, Topic 6 Message 31 Wed Jun 24, 1992 CBM-ED [e.g.bell] at 22:14 EDT Doug: The reset message that comes back from Jiffy DOS... what exactly is the text. I just did an ML utility that reads that string to identify the string. If the length is changed, I am in deep something because the drives won't be correctly identified. I *hate* when that happens! :-( p.s. My program is looking for the drive id (i.e. 1571, etc.), but I don't parse the whole string. I check a certain number of characters back from the end of the string.... eight I believe. ......1581,00,00<cr> ^ It checks the byte referred to above. Am I gonna have to make some algorithm changes. >>sigh<< Just once I hope I get a break! ------------ Category 12, Topic 6 Message 32 Thu Jun 25, 1992 CMD-DOUG at 08:25 EDT Just do this, assuming the drive is device #8: @#8 (press RETURN) @UJ (press RETURN) @ (press RETURN) You should see a message on the screen. If 'JiffyDOS' is part of that message, then the drive is JiffyDOS equipped. If not, then it isn't. And if the drive isn't device number 8, change the 8 in the first line to whatever device number the drive IS set for. ------------ Category 12, Topic 6 Message 33 Thu Jun 25, 1992 CBM-ED [e.g.bell] at 18:50 EDT Assuming you are replying to me, that information doesn't help, Doug. But I thought later after I logged off that Jiffy DOS is easily disabled. When you disable it, does the default DOS error message for a reset return, or does the Jiffy DOS message remain. I think in the next version I do, I will just parse the message from the start. That way this won't come up. Actually, though, if the last thing in Jiffy's message before the comma that precedes the track/ sector part of the error message is the drive type, I'm ok! Did that make sense, and is it correct. Incidentally, Jiffy DOS *is* on my list of things to get when I can. I need an Eprom burner first, tho. ------------ Category 12, Topic 6 Message 34 Fri Jun 26, 1992 HOWIE-CBM at 02:01 EDT Ed, I'll leave the programming part to you, but I can help out with what the command channel returns after a reset is sent: 73,(c) 1989 jiffydos 6.0 1581,00,00 Hope this is what the progam wants. :) Howie ------------ Category 12, Topic 6 Message 35 Fri Jun 26, 1992 CMD-DOUG at 02:11 EDT Sorry Ed, I let myself get your message confused with someone elses. In the case of Commodore drives, yes, the last part of the message does contain the drive model number as usual. In the case of CMD devices, this is not what happens. I think I might have uploade my POLL DEVS.BAS file up here if you want some info on how to really identify drives correctly. ------------ Category 12, Topic 6 Message 36 Fri Jun 26, 1992 CBM-ED [e.g.bell] at 19:52 EDT Thanks Doug, but Howie gave me the info I needed, and I am pleased! Jiffy DOS should work perfectly with my program because it leaves the drive identifier in the last position before the track/sector part of the DOS error message. As for the hard drives, my prg won't even pretend to support them, but then, sounds to me like you guys got the same ground covered anyway. Soo.... Thanks Howie, and thanks to you , too, Doug, because of how quick you responded. BTW, there is a *LOT* of discussion on FIDO wrt your hard drives and RAMLINK supporing CP/M. I am very much ignorant in all this, so I can't contribute anything to the discussion out there, but for what it is worth, CMD is well- appreciated and much-discussed. Your presence on GEnie has been mentioned there too! ------------ Category 12, Topic 6 Message 39 Sun Jul 11, 1993 A.PEROTTI at 20:27 EDT I have just installed JiffyDOS on my 128D and 1581. So far it is really great! I do have one question, though. On page 37 of the manual, the @N2 command is described. I don't understand it. Is the purpose to format a 1571 disk on a 1571 while it is in 1541 mode? Or is the purpose to exploit some other mode of operation? The book states, "This command helps take advantage of the double-side 1541- mode operation provided by JiffyDOS". What is this mode and how do I switch from one side to the other? I seem to remember reading somewhere about using the 1571's other head to create "flippies" that don't need to be flipped, but I can't for the life of me find it now! This is probably a rather trivial question for all you pros out there! Tony P. ------------ Category 12, Topic 6 Message 40 Sun Jul 11, 1993 CMD-DOUG at 20:33 EDT The @N2 command is useful for formatting disks when using a 1571 hooked to either a 64 or a 128 in 64 mode. The regular format command, when in these modes, only produces a single-sided disk as on the 1541. If you do your formatting from 128 mode all the time, then you can ignore the @N2 command. ------------ Category 12, Topic 6 Message 41 Sun Jul 11, 1993 C128.JBEE at 23:32 EDT You could format each side of a 1571 as a 1541 using the H0/H1 command but since it really is not a flippy it makes it impractical to use. A few BBS programs used it, but besides its novelty and maybe the fact that you can skirt some DOS file limits, it is not worth the bother in my opinion. Just one of those neat things that serve not purpose :D ------------ Category 12, Topic 6 Message 42 Mon Jul 12, 1993 HOWIE-CBM at 15:56 EDT The H0/H1 are most useful when using copy protected programs like the Pockets. Any one version of the Pocket uses only one side of the disk. If you are willing to re-format the other, you can have a 2 sided flippy that does not require flipping. The *BIG* reason this never became a popular "trick" is that altho this ran on a 1571, access to that second side had to be in slow serial mode. Burst was not possible on a 128 in its 128 mode. Thinking about it now tho, I quess if I had JiffyDos at the time access would have been acceptably fast. Ah well... I didn't JiffyDos all those drives until after I got RAMLink. And with RL, there is no point going to these lengths to recover an extra 160k of on-line storage, as in the past. Howie ------------ Category 12, Topic 6 Message 43 Mon Jul 12, 1993 A.PEROTTI at 22:30 EDT Thanks for the response. I see that this format is of limited use. The primary reason I'm interested is that I think it may provide a solution to my question about a 4-disk-side game (see my post in cat 5 top 31). How is the H0/H1 command used? I can't seem to find it in the 1571 manual. I presume that to use non-fipping fippies you must be able to send disk commands from within the program you're running.(?) Tony P. ------------ Category 12, Topic 6 Message 44 Mon Jul 12, 1993 CMD-DOUG at 23:20 EDT That command is listed. It's one of the utility commands sent with 'U0>'. See page 87 of your 1571 manual. This on't really help you solve your problem though, as you won't be able to send the disk command to switch sides while in the middle of your game. Sorry. ------------ Category 12, Topic 6 Message 45 Thu Aug 05, 1993 CBM-ED [e.g.bell] at 19:24 EDT Help!!!!!!! I went to Radio Shack today to buy new tips for my soldering pencil, a new solder remover, and some side cutters to cut out the kernal chip in my 64c. The only thing they did not have was a low profile 24 pin IC socket, which is the reason I bought all the other stuff. I'm going to proceed with the job, but does anyone know anywhere else I can get the socket. This is turning into a PROJECT! aiiiiiiiii! (Not because of CMD. I ordered the stuff last Friday sending in an order and a money order and got it back Wednesday the following week) p.s. Doug... did you remember that cable for the battery pack? ;) Thanks! I need the one with the female end. I got the one with the male RCA type end. ------------ Category 12, Topic 6 Message 46 Thu Aug 05, 1993 C128.JBEE at 23:51 EDT RS doesn't carry 24 pin sockets? ------------ Category 12, Topic 6 Message 47 Fri Aug 06, 1993 CBM-ED [e.g.bell] at 03:25 EDT No, and the guy there told me that probably no RS would, tho I am not going to take that as gospel at this point. I looked at the solder joints on that socket today... I'm intimidated! ------------ Category 12, Topic 6 Message 48 Fri Aug 06, 1993 CMD-DOUG at 03:45 EDT In a pinch, you could get a 28 pin one and just cut off the extra pins. The socket won't care. :) (Yes Ed, I remembered you). ------------ Category 12, Topic 6 Message 49 Fri Aug 06, 1993 HOWIE-CBM at 04:00 EDT Ed, If still needed I ought to be able to pick up a 24 pin socket easilly. Let me know. For removing solder I, long ago, got one of those dedicated desoldering irons. This one has a spring that you set. Once the solder is running, a press of its button sucks it up. Worked great when it came to removing the 2 VDC ram chips. If this might assist in your project, I am willing to put it out on loan. :) Howie ------------ Category 12, Topic 6 Message 50 Fri Aug 06, 1993 CBM-ED [e.g.bell] at 12:26 EDT I got sockets this morning and bought a solder vacuum last night. I am not sure the tools will make the difference here, but I'm going to give it a try. If it fails, I'll go from there. I wanna get it fixed for the kids cuz I made them pay for the chip. heheh ------------ Category 12, Topic 6 Message 51 Fri Aug 06, 1993 CBM-ED [e.g.bell] at 18:33 EDT Doug: As per our call today, I got the sockets, removed the chip, and soldered the socket in. As far as I know I did a beautiful job, judging by the appearance alone. I doubt you could tell the difference between mine and whatever did the rest f the solder connections on that PC board... however.... little did I know during all of that that the final insult was awaiting me. I went by the included diagram religiously... picked out my computer, as there were two diagrams for the C64C, and it was obvious mine was the one on the left. I did not take the chip out of the foam because I don't like to handle them any more than absolutely necessary. Have you guessed yet.... The chip I received is a 28 pin chip and my kernal is a 24 pin, going strictly by the diagram included in the instructions as to location and general layout. The only upside that I can see in all of this is that I wasted no steps since I'm going to need that socket in there finally anyway, but DARN! I obviously have so send the chip back, but can you give me any idea what happened? I sent the serial number in with the order as requested. It is CH2010244C. Is my unit goofy wrt the serial number or was this just a mixup? Anyway... I am soooooooooooo frustrated! ------------ Category 12, Topic 6 Message 52 Sun Aug 08, 1993 HOWIE-CBM at 09:50 EDT ouch! I agree! I would sure be frustrated. After all the detailed work, and time, and then for the final real test to confirm the triumph, only to find out popping in the chip will now be postponed due to excess legs... <sigh> Howie ------------ Category 12, Topic 6 Message 53 Sun Aug 08, 1993 CMD-DOUG at 10:24 EDT Chalk it up to Commodore, who did a bit of mixing over a couple thousand serial numbers. We can usually narrow it down by the number, but yours lies in that range where it could be either. ------------ Category 12, Topic 6 Message 54 Sun Aug 08, 1993 HOWIE-CBM at 10:36 EDT hey! Congratulations Ed!!! You have a *SPECIAL* computer!! :) Howie ------------ Category 12, Topic 6 Message 55 Sun Aug 08, 1993 CBM-ED [e.g.bell] at 11:47 EDT HH> After all the detailed work, and time, and then for the final HH> real test to confirm the triumph, only to find out popping in HH> the chip will now be postponed due to excess legs... And you can't imagine what a thing it was for me to actually go to the extreme length of doing something like this! arrrrgggggghhhh! DC> Chalk it up to Commodore, who did a bit of mixing over a couple DC> thousand serial numbers. We can usually narrow it down by the DC> number, but yours lies in that range where it could be DC> either. Well, if it were any other company, I would be pitching a royal tantrum, but you guys have been so great I figure it has to be something very unusual. I'm just bummed that I have to wait to use anything that you got to me so quickly. :::: sigh :::: ------------ Category 12, Topic 6 Message 56 Tue Aug 10, 1993 CBM-ED [e.g.bell] at 11:06 EDT Doug: Don't know who I spoke to yesterday, but he said he would ship the chip immediately. I shipped the one I got back yesterday first class and insured it for $50 for my own peace of mind. Tell whomever it was I said Thanks! ------------ Category 12, Topic 6 Message 57 Tue Aug 10, 1993 CMD-DOUG at 12:15 EDT Will do, Ed. Glad they didn't have a problem with doing that for you, as under normal circumstances it is against policy to do so (just because we've had a lot of users who abused this and never returned the original part). Justed wanted you to know, though, that I couldn't authorize it to be done that way myself, had to come from somebody in charge. ------------ Category 12, Topic 6 Message 58 Tue Aug 10, 1993 CBM-ED [e.g.bell] at 13:20 EDT I don't know who it was that I spoke to, and ordinarily might have hesitated telling anyone about the snafu, but part of what makes a company great is not that they never make mistakes (even tho this was apparently not CMD's fault), but what they do to correct them, and you guys have certainly shone in this regard also. I figure I'll be getting the second chip faster than some companies have delivered an original order. As I said before, thanks, and I'll make sure people know how pleased I am in spite of the chain of events! ------------ Category 12, Topic 6 Message 59 Wed Aug 11, 1993 CMD-DOUG at 01:20 EDT Thanks, Ed. Just sorry to see any problems, but the sooner they are fixed, the better off everyone involved is. ------------ Category 12, Topic 6 Message 60 Wed Aug 11, 1993 AMFORD at 22:23 EDT I have a question about Jiffy Dos for the MSD drives. Is there any speed up with the MSD-2 drive to drive copy with Jiffy Dos installed? Is JD compatible with the CHIP Level Designs auto-copy roms? (I am going to actually get that pair of chips some day!) ------------ Category 12, Topic 6 Message 61 Thu Aug 12, 1993 C128.JBEE at 03:05 EDT With the JD roms, the MSD-SD2 is just as fast read and writing (non-burst) as a fast serial 1571 and it is fast in CP/M mode too. I remember using the backup command once and a disk copy taking a minute or two, which is just about as fast as not using it with JD. Of course the auto-copy ROMS are 22 sec (verify on) and 15 sec (verify off) to back up a disk. ------------ Category 12, Topic 6 Message 62 Thu Aug 12, 1993 C128.JBEE at 03:06 EDT >Is JD compatible with the CHIP Level Designs auto-copy roms? (I am going to >actually get that pair of chips some day!) No, they occupy the same sockets. ------------ Category 12, Topic 6 Message 63 Fri Aug 13, 1993 CMD-DOUG at 04:27 EDT Heh, often JBEE is more the resident expert on JD and MSD than I am. Thanks for supplying the answers, JBEE. :) ------------ Category 12, Topic 6 Message 64 Fri Aug 13, 1993 C128.JBEE at 17:03 EDT You're welcome :) ------------ Category 12, Topic 6 Message 65 Mon Aug 16, 1993 AMFORD at 00:02 EDT Shoot! I was hoping to get that drive to drive copy done faster! :) Thanks for the info. ------------ Category 12, Topic 6 Message 66 Mon Aug 16, 1993 C128.JBEE at 13:42 EDT You could write your own drive copier if you wanted since the MSD drives have more than enough RAM for a disk to disk copier. I believe the MSD memory locations were in one of the MSD archives I uploaded. ------------ Category 12, Topic 6 Message 67 Sat Aug 21, 1993 AMFORD at 00:05 EDT Sorry JBEE! I am ENTIRELY to lazy to actually code anything on my commodores. ------------ Category 12, Topic 6 Message 68 Tue Sep 14, 1993 K.BRANDON (Forwarded) Here are a couple of what I think are bugs in JiffyDs 6.01 that I thought I would bring to attention of everyone. Has anyone else noticed anything like this? 1) If the @d or @t command is used with a single-character filename on the 1571 or 1581, many times the file that is read is not the named file, but instead is the first file in the directory. This behaviour can be defeated by using the @u9 reset command, but it does otherwise occur in an unpredictable manner. 2) The screen print command (@p) can give an output that does not accurately reflect the screen. Run the little program below and do a @p on the output. This program was a screen-layout aid that I wrote in support of something else. 10 c$="0123456789012345678901234567890123456789" 12 print"[clear][down]"c$; 20 fori=1to38 30 a$=a$+" " 40 next 50 data1,2,3,4,5,6,7,8,9,0,1,2,3,4,5,6,7,8,9,0,1,2,3 60 fori=1to22 70 readb$:printb$a$b$; 80 next:printc$"[home][12 down][16 right]Center" The above is for the 64. ------------ Category 12, Topic 6 Message 69 Tue Sep 14, 1993 CBM-ED [e.g.bell] at 03:08 EDT KB: I moved your post here from the NovaTerm category because it is more appropriate here. As far as your observations, I don't use the commands that much, and don't have any 1 character file names. I have noticed sometimes, when doing a screen dump with the CTRL-P command, that I get a LOT more lines to the printer than there could ever be on a screen. I would say about 10 or 20% of the time this happens. I never questioned it, attributing it to my interface or something in my setup, but your post reminded me of it. ------------ Category 12, Topic 6 Message 70 Tue Sep 14, 1993 H.HERMAN1 at 07:14 EDT KB, Well, unlike Ed, I use one character filenames, especially if the keyboard buffer calls them for auto-backup routines. I personally have nothing against one character filenames. If CMD were to do an upgrade of JiffyDos, and while this is no bug, my one suggestion would be to replace the filecopy routines for REL files with those used by FCOPY. :) Howie ------------ Category 12, Topic 6 Message 72 Sat Oct 02, 1993 P.KELLER5 [Diesel II] at 01:01 EDT Well, after years of hearing about JiffyDOS, I decided to finally buy one for my 128D, and my 1581 & 1571 additional drives. Well, I have so far only seen one program that loaded fast and that one was Omega Q the utility program from Q-Link. And found that a few programs will not load with JiffyDOS on (The Simpson's Arcade Game, Xenophobe so far) I'm just wondering what other programs load fast? Also, when I read the ad about buying JiffyDOS, it says have the serial numbers ready, but when I ordered them, no numbers were asked. Just wondering, thanks! ------------ Category 12, Topic 6 Message 73 Sat Oct 02, 1993 CBM-ED [e.g.bell] at 03:22 EDT The most dramatic speed increase seems to me to be in 64 mode. I experienced the same thing you are... so many had built up my expectations that nothing could have lived up to them. However, if you want to see a dramatic improvement in speed, make an SFX with JD installed. It went so fast, the first time I saw it (the 2nd stage) I thought something was wrong. ------------ Category 12, Topic 6 Message 74 Sat Oct 02, 1993 CMD-DOUG at 22:58 EDT As Ed mentioned, speeding up of program LOADs by JiffyDOS is more obvious in 64 mode. 128 mode does benefit, but more in file SAVEs and in reading and writing of data files when using 1571 or 1581 drives. Even so, there are cases in 64 mode where little or no appreciable speed gain will be observed in program LOADs - such as with programs which have their own fastload routines, or programs which load using inefficient methods (like block-reads). Some programs may skip using the standard Kernal routines for disk access, and thus by-pass JiffyDOS altogether. And some programs may jump directly into routines in the Kernal or DOS ROMs, and if they perform these jumps into areas that have been changed, they may prove incompatible. If you find a program that falls into this latter catagory (there aren't a lot, but some), try performing an '@Q' command prior to loading them instead of turning JiffyDOS off entirely - this may clear up compatibility issues with some of them while allowing them to load with the JiffyDOS speed-up routines still enabled. Serial numbers are only needed for 64-type computers - as there are some 64's that require a different ROM than others. All other computer and drive ROMs can be determined strictly by model. ------------ Category 12, Topic 6 Message 75 Tue Oct 12, 1993 E.WHITAKER2 [Scormus] at 01:44 EDT Is the C-65 computer available from Grapevine group supported by Jiffy-Dos and does anyone know just what this computer is? The ad says it is basically a c- 64 with an internal 3.5 inch drive. Thanks in advance for your reply. ------------ Category 12, Topic 6 Message 76 Tue Oct 12, 1993 CMD-DOUG at 15:07 EDT Indications are that these are Alpha test units of the C65. There are only a very limited number of these, and they have no documentation. There are also some custom chips installed that never went into actual production, so some parts will not be replaceable should they go bad. We won't be doing a version of JiffyDOS for this, no. ------------ Category 12, Topic 6 Message 77 Tue Oct 12, 1993 CBM-MARK at 21:58 EDT For more information on the C65 read topic #5 in Category #2. SET 2 REA 5 ------------ Category 12, Topic 6 Message 78 Thu Oct 14, 1993 D.TUOMI [Doctor] at 03:17 EDT