| |
Ymgve
Registered: May 2002
Posts: 84 |
In what format should I upload releases?
When I upload a release to CSDb, what is the prefered format? If it's just a singlefile crack/demo it seems more logical to just upload the PRG, but then I have to rip apart spread disks.
But if I upload the whole D64, it's possible that there's other stuff on the disk too, so when you autostart the D64 you will get something else than expected.
What's the best way? |
|
| |
Scout
Registered: Dec 2002
Posts: 1570 |
In .D64 or .T64.
This way you preserve the original filenames.
.prg's fuck that up.
Also split the different releases from one disk in seperate d64's (or t64's).
Edit: and yes, it can be a tedious job if you want to
do it properly :-/
|
| |
Ymgve
Registered: May 2002
Posts: 84 |
Doesn't creating a new D64 have the same problem as PRGs, though - that it takes the release out of the spread disk?
Maybe I should just upload both the PRG and D64 :) |
| |
Scout
Registered: Dec 2002
Posts: 1570 |
Quote: Doesn't creating a new D64 have the same problem as PRGs, though - that it takes the release out of the spread disk?
Maybe I should just upload both the PRG and D64 :)
If you use the right tools you can preserve everything.
64Copy V4.3 Beta 3 is highly recommended for this job. |
| |
iAN CooG
Registered: May 2002
Posts: 3186 |
Quote: If you use the right tools you can preserve everything.
64Copy V4.3 Beta 3 is highly recommended for this job.
Also remember to WIPE files and not only delete them, if you split one d64 into more d64s, to allow better compression. Deleting only keeps the files on the disk, you know. |
| |
The Overkiller
Account closed
Registered: Mar 2002
Posts: 342 |
C64copy is the best but you can use this one too D64 Editor V0.028 if you like it to manage .d64 or upload .prg files into a .d64 |
| |
Rough
Account closed
Registered: Feb 2002
Posts: 1829 |
I usually take the crack of a spread disk, copy it into a blank .d64 file and then use a dir editor to transfer the directory design into the new .d64. |
| |
Tim
Account closed
Registered: Mar 2002
Posts: 467 |
helpfull post this!
i'm just transferring a few 100 disks myself at the moment.
I was wondering, can you use a deformatter (like micron's or other/better ones you can suggest) on transferred .d64 files?
I ask, because i did transfer 'blank' sides to .d64 just incase I might have left old files/games/whatever that seemed pointless to keep in those days but that might actually still be on the disk.
Also I am wondering maybe the obvious, but wouldn't it be wise to zip .d64 or .d81 files before upping them to csdb? I notice several people don't do that (including myself by accident once or twice).
|
| |
Marauder/GSS
Account closed
Registered: Jul 2006
Posts: 224 |
StarCommander has a also function to check d64 images for errors and/or deleted files, and also can try to repair them (deformat)... You can also easy create new empty d64 and copy the stuff from other images over etc.
d64/t64 is ofcourse the prefered format! I think disk-layouts of spreaddisk is not that "really important thing" (at least for me, though it's nice to have - not a must), more to preserve the filenames - which you'll do with d64/t64 |
| |
wreg
Account closed
Registered: Mar 2004
Posts: 679 |
pls try to preserve as much as you can!
filenames, dirlayout, EVERYTHING!
there is always someone who wants to have this :-)
so:
if you have the time, spend it on copying files with a decent tool, so you keep the original filenames
if you have even more time, copy the dirlayout as well
if you cannot 'afford' it, think about uploading the spread-disk as well, so someone can do this work later... |
| |
Ymgve
Registered: May 2002
Posts: 84 |
Another good thing about preserving the original images is that it allows somebody to dig deeper into the disk later on. There's been quite a few disks that had extra files on them not shown in the directory listing. |
... 25 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 | 4 - Next |
