Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > CSDb Feedback > Please stop "cleaning" disk images
2019-03-20 00:30
chatGPZ

Registered: Dec 2001
Posts: 11088
Please stop "cleaning" disk images

... or at least after you do so, test if the damn release still works after doing so. not seldomly there is other stuff on the disk that is needed - and its not necessarily obvious, or even visible in files. it really sucks to find those non working things when it is obviously the result of someone trying to "optimize" the image. ideally also attach the non cleaned image - that also keeps the context with the other games on the disk intact, which is sometimes kinda interesting to see.

thanks.
2019-03-20 11:06
hedning

Registered: Mar 2009
Posts: 4551
Yes: Make sure all files (can be rips, pics, docs, dirart) from the release you are uploading are there, and test the release before uploading.
2019-03-22 18:06
Thierry

Registered: Oct 2009
Posts: 47
Good point, I have several releases that are not in CSDB, I'll be a good idea to load the image without cleaning, image.no clean.d64


retrocomputacion.com

Argentina
2019-03-22 22:19
bugjam

Registered: Apr 2003
Posts: 2467
Great, bring them on! :-)
2019-03-23 09:24
TheRyk

Registered: Mar 2009
Posts: 2035
yeah especially if download files are flagged "broken", upload the complete image in question as transferred, not only .prg and no modifications
2019-03-23 09:54
bugjam

Registered: Apr 2003
Posts: 2467
I opt for both, though - a cleaned version, to make life for the SID checkers like Fred easier, and one original version.
2019-03-23 17:44
Mr.Ammo
Account closed

Registered: Oct 2002
Posts: 228
Quoting TheRyk
yeah especially if download files are flagged "broken", upload the complete image in question as transferred, not only .prg and no modifications
It seems that the broken property can only be used when the release concerns a crack. While it should also be used for other releases that break, people tend to use the corrupted files flag instead. Which is a no-no according to:

Quoting CSDb rules
The "Goofs" field and "broken" tag is aimed at the scene release in question. A goof is meant to document bugs in the release; for a crack that means bugs inflicted by the cracking group - not bugs that is in the original game. The "Broken" tag is used for signalling a broken release, again inflicted by the crackers or coders for example. For demos "broken" can be used if a release crashes and a newer version that works exist. Don't confuse the "broken" tag with the corrupted files (a bad copy, where the disk is trashed), that is covered and tagged editing the file in question when uploading.
2019-03-23 21:38
chatGPZ

Registered: Dec 2001
Posts: 11088
No. these are two different flags. one is per file (and can be used on any file) and its for marking actually broken files (not broken releases). the other is for marking broken cracks, and that is for marking fucked up cracks, not broken files.
2019-03-23 22:42
bugjam

Registered: Apr 2003
Posts: 2467
"For demos "broken" can be used if a release crashes and a newer version that works exist." That refers clearly to the "broken" tag (like for cracks), not the "corrupted" flag for the download.
Good point, in fact, although those cases are probably rather rare.
2019-03-24 01:03
Slajerek

Registered: May 2015
Posts: 62
Especially my dumb spread notes from '90ties :D
2019-03-24 09:50
Fred

Registered: Feb 2003
Posts: 282
Quote: I opt for both, though - a cleaned version, to make life for the SID checkers like Fred easier, and one original version.

This is the wrong reason but thanks for adding cleaned disks :-)

The real reason for adding cleaned disks is of course that the release entry is about a release and not about a spreaded disk where the release was on. There are other sites for dumping disk images.

We have many comment fields for a release entry for preserving info that is found on a disk or on a release. No need to add uncleaned disks for this.

Anyway, always add a clean disk to a CSDb release entry. The uncleaned disk might be added but really not needed. It only makes the release entry 'dirty'.

Bottom line is that after cleaning a disk, always test the release and double check if all the files from the release are present. Also check for useful info on the uncleaned disk that can be added to CSDb.

If you're unsure that you missed something from a disk, you can always add a comment from which disk of which collection the release was found.
 
... 21 posts hidden. Click here to view all posts....
 
Previous - 1 | 2 | 3 | 4 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Zeus
Matt
Ko-Ko
Nordischsound/Hokuto..
MagerValp/G★P
deetsay
Guests online: 356
Top Demos
1 Next Level  (9.8)
2 Mojo  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 No Bounds  (9.6)
6 Comaland 100%  (9.6)
7 Uncensored  (9.6)
8 The Ghost  (9.6)
9 Wonderland XIV  (9.6)
10 Bromance  (9.6)
Top onefile Demos
1 Party Elk 2  (9.7)
2 Cubic Dream  (9.6)
3 Copper Booze  (9.5)
4 Rainbow Connection  (9.5)
5 TRSAC, Gabber & Pebe..  (9.5)
6 Onscreen 5k  (9.5)
7 Dawnfall V1.1  (9.5)
8 Quadrants  (9.5)
9 Daah, Those Acid Pil..  (9.5)
10 Birth of a Flower  (9.5)
Top Groups
1 Booze Design  (9.3)
2 Nostalgia  (9.3)
3 Oxyron  (9.3)
4 Censor Design  (9.3)
5 Crest  (9.3)
Top Diskmag Editors
1 Jazzcat  (9.4)
2 Magic  (9.4)
3 hedning  (9.2)
4 Newscopy  (9.1)
5 Elwix  (9.1)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.217 sec.