JDownloader Community - Appwork GmbH
 

 
 
Thread Tools Display Modes
  #1  
Old 04.04.2010, 20:44
drbits's Avatar
drbits drbits is offline
JD English Support (inactive)
 
Join Date: Sep 2009
Location: Physically in Los Angeles, CA, USA
Posts: 4,437
Default Minor problems in 10957

Jiaz said to work hard testing this version.

I do not expect all of these to be fixed in the next Stable release. Some should wait. I will continue adding to the end of this message until the next version appears. I do not know which are important enough to report in BugTracker (several are already in BugTracker). If a decision is made to not implement or to delay or a BugTracker ticket is created, please add that to this thread. I will strike-out the item here.

1) When a file is deleted, different hosts display different messages. The messages should be consistent.
Recommended message: Deleted or Deleted: substatus.
If a file is found, the status of "Found" is recommended.
If the status is really unknown, then it should be displayed as "Unknown" or "Unknown: substatus". Any details from the host should be shown in the properties, not the grid.
Rapidshare, Hotfile: [Not Available] (what are the brackets for?)
Depositfiles: Not found
This does not require changing the plugins. There is a discussion thread that settled on these as the recommended replacements for "Online", "Offline", and the other inconsistent or confusing status names.
This is to assist the LinkGrabber part of status consolidation and to help prepare for the Event Manager.

2) Rapidshare sometimes shows "Unknown file size" for files that are "[Not Available]", and sometimes shows a length. If a file is not available or not found, the length should be either the file's actual length or 0. It should be consistent across all hosts. The database still contained the length when the status was changed to "[Not available]" This does not require changing the plugins.

3) In a package with 3 mirrors for each of 8 parts, when all parts are deleted, right clicking on the package shows "Resume (8)" instead of "Resume (24)" Apparently "[Not Available]" locks the link (and displays the do not enter red icon), but is not an error. It looks like "Not found" is what is being counted. All of the other counts are 24.

URLs in this package (1), (2), (3), (5):
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**

4) [Not available] does not mark the package with the orange error dot.
Sample URL:
**External links are only visible to Support Staff****External links are only visible to Support Staff**

5) Reset or Resume on Deleted links does not always change the display of the link until the mouse is moved over the line containing the link.

6) The first link shown above, when "Reset" and "Force Download", displays a status of "TOS violation. File removed by rapidshare" and the No Entry red icon. It also causes the orange dot on the package, while it did not when the file was [Not Available].
The status should be "Deleted" with a substatus of "censored" (Displayed as Deleted: censored) and the explanation (as currently displayed) should be in the properties.

7) Filefactory and Mediafire sometimes download and sometimes display "Plugin error (Out of date)".
7a) This status message is overused. It is often incorrect. The correct status would be "User needed: unexpected response"
7b) The Mediafire was an attempt to start 4 links at the same time (an entire new package). Three of the 4 started, one gave the spurious message.

8) Links are being marked with a relatively new status: "File loaded from other source". It is not clear where this is coming from or when it is generated. If it is generated when the file actually exists, the "File exists" status (a permanent error) should be displayed. If it is generated when it is discovered that a mirror is downloading the file, this is a bug.
8a) In any case, disabling the link is a bug. This should be reserved for users disabling links.
8b) If links are going to be automatically disabled, the text should be clear, only the background grayed.

Sample links for (7) and (8)
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**

9) The properties pane still covers the info pane on both Download and Linkgrabber.
9a) The Linkgrabber setting "Show info panel" does not seem to do anything.
9b) The Download info pane is still missing the number of active downloads. This should be the number that have begun downloading file data, not including the number that are trying to connect.

10) Is the KB Loaded and the speedometer based on the TCP packet payload transferred or the data processed? It still looks rough when the system has other programs running (even if they are not using the network). This should be explained.

11) The most important status text is still not kept between sessions. It apparently can also be lost when packages are merged. Keeping status is especially important when the link has been automatically disabled.
11a) Some messages are kept between sessions that should not be (temporary messages like connecting).
11b) For the future, I suggest three status fields per link (status, substatus, and host message). If necessary, temporary messages should be kept in the DB, but separate from the Status fields (it can be the "DL_current_display" field, and identified as temporary in the DB).

12) Passwords are still not always kept when packages are merged. I don't know if the "Move the password to the link" solution is broken or we need to move to a "always add the manual password to the auto-password list" approach.

13) Not a bug, just so we have it on record. JD slows down noticeably at around 19 000 links. Packages with over a few hundred links are hard to work with, but packages do not slow down with size, at least up to 7000 links.

14) We still have to click on a package for Find, Move to top, and Move to bottom.

15) When turning off automatic reconnection, a disturbing warning is displayed (too strong). It is missing the "Do not show this again" check box.

16) The confirmation for Reset should show the number of files (as I am told that it did in early versions). It is missing the "Do not show this again" check box.

17) A lot of the on-line documentation is from before the adoption of tabs.

18) Sometimes the Captcha pop-up captures the keyboard input while it is not the selected window. This just happened with uploadbox, but I think it is a general problem. If I am typing a word when it pops up, it captures part of the word. If the keyboard is quiet at the time, it seems to wait.

19) TCP stability appears to be improved. I seem to be able to run 18 downloading links concurrently on a 160 KB/s connection (a total of 34 connections, because the 4 mediafire downloads are using 5 chunks each). I am running while using FF and doing file copies and unrars I have restricted JD to -Xmx384m (about 440MB private bytes).
19a) I can confirm that Max. Con., Max. Dls., and Maximum simultaneous downloads per host are all working correctly.

20) Dragging packages leaves the wrong package highlighted. It should be the package that was dragged, not the package before or after. I believe this is a problem with Links as well.

21) Right clicking should not change the highlighted link or package, unless there is none highlighted. When a package is open, right clicking on the package header changes the highlight to that line. This makes working with a subset of links more difficult. Eventually, it might be best to have a selection of links, independent of the packages (e.g., select links in multiple packages, right click, move to new package).

22) Files are supposed to be checked to make sure JD does not download extra HTTP, HTML, or XML at the beginning of the file. Due to a bug in 9.579, I have 4 links to HTML files instead of the RAR files they claim to be. Since the extension does not match the file signature, this should have been reported by JD as a bad link. Instead, it was reported by unrar as "Extract failed: ASpb.rar is not RAR archive" (sic.).
22a) Part of the problem is the HTML kludge. JD sometimes removes the .HTML or .HTM without checking that there is no HTML file there. This could also be related to the recent fix to avoid messing with the extension of XML variants (such as .docx, .stl). I know that sometimes we have to remove the .HTML to avoid a loop or a 40x, but those can be dealt with better.
22b) We have a list of file header signatures and the proper MIME-type (content-type) and extension for that signature. If JD finds a mismatch, it should act then. Initially, it would be enough to check for about 20 binary types (zip, rar, 7z, tar, gz, bz2, common Linus installers, riff (AVI), mp3, mkv, mp4, gif, jpeg, png, and so on), HTML, XHTML, and XML signatures (<H, <!, or <?). If it receives a page that does not match the content-type, then it is an "Unexpected data error" (which we now report as plugin out of date, but should be retryable). This may have to wait until the host plugins are restructured into subclasses or callbacks of JDhost_plugins (or whatever the class name will be).

23) Not being able to sort on status makes large packages much harder to deal with.
23a) For example (probably not in this release):
finished (downloaded and extracted or hash checked): 100, (Green Check mark icon)
downloaded: 90, (Blue check mark)
downloading: 80, (Green down arrow)
negotiating download: 75, (displayed as downloading)
HTTP connecting: 70, (displayed as downloading)
waiting in the queue: 60, (nothing to display)
Unknown: not checked (and similar benign status, such as duplicate link): 50 (blue link)
in a wait that affects all links for a host: 45 (blue clock icon?)
retryable (if it has not retried yet): 40 (blue link), retries exhausted (example of resumable)
waiting for user (resumable): 30 (blue clock?)
user disabled link: 25 (shown by blue lock icon?)
Host busy (including no slots): 20 (orange clock icon)
Unexpected data: 15 (orange link?)
downloaded, but post-processing error: 10 (orange down arrow)
"bad link", Deleted (and other permanent errors): 5 (broken orange link)

Unexpected data is an extended form of what currently generates Plugin error (out of date). It includes
* data that should be on the page, but cannot be found,
* content-type (MIME type) does not match data,
* extra html page that JD does not know how to handle, usw.
Eventually, extra html pages should be handled with the same regex as other pages. Buttons marked Skip or Proceed should just be followed. Defaults should be used for missing data. When things are moved around on the page or moved from page to page, JD should be flexible enough to handle it.

Background color of filename field and status field should vary with status. The specific colors should be defined in the style or a style_name.inc or rc file. (default could be red=255-2.5*value, green = 2.5*value, blue=192 this is magenta through cyan).

24) Sometimes, a link will stop downloading, but the green light with a check mark will not appear, because the file hasn't finished downloading. There is no status message or symbol to explain the situation. The Progress column shows the same two numbers (as do Loaded and FileSize, but the numbers are not the correct file size). The Part file is there instead of the regular file name. It appears to happen most when there is no Hash and the file is a media file. I seem to remember that the downloaded column tooltip for a link used to be the number of bytes downloaded. The tooltip for the filesize column should also be in bytes. In this case, the file was in x7.to, and so I will have to reset and redownload it.
Today's Sample Link: **External links are only visible to Support Staff** Original Link from KatzForums: **External links are only visible to Support Staff**



Log attached

Last edited by drbits; 05.04.2010 at 08:18.
  #2  
Old 06.04.2010, 02:11
drbits's Avatar
drbits drbits is offline
JD English Support (inactive)
 
Join Date: Sep 2009
Location: Physically in Los Angeles, CA, USA
Posts: 4,437
Default Continuation of Minor problems in 10957

25) When several packages are selected, right clicking and choosing "Check Online Status" does not add the orange mark to the packages containing deleted links. This means that users have to scroll through all of the packages to find the problem links.

26) When part1 of an archive has been downloaded, JD unrar will try to extract the archive, even if the rest of the volumes have not yet been downloaded. This is repeated after each volume is downloaded. The extractions fail (and mark the links as "Extract Failed") until the final volume is downloaded. This is O(n^2) work when the volumes are in numeric order (as they normally are). BUGTRACKER

27) Putting the URL of a page containing CNL buttons into Add URLs will effectively push all of the buttons if nothing is found and One level deeper is triggered.

28) There appears to be no way to create a JDC containing part of a Links List instead of the whole list. It could be useful to have a container format that keeps the links encrypted, requires a password to open, and is independent of the JD.org server.

29) When a link is added from the clipboard and the link is a redirection link, JD does not always detect and use the redirected link. Fake example:
**External links are only visible to Support Staff****External links are only visible to Support Staff**
29a) When Anchor text is clearly a link or an href is detected, but the rest URI is not usable by Linkgrabber, Linkgrabber should treat the URI as an ordinary string to search for URLs and passwords.

30) Although Linkgrabber finds some passwords with colons (pass: jeronimo), it does not appear to find passwords with equal signs (pass=jeronimo). I haven't checked, is it sensitive to whitespace around the colon?

31) JDownloader or its installer should identify the processor type and check that the current JRE matches.

32) Links and log for errors, such as Unexpected Data (Plugin error, out of date), should be automatically submitted, with user permission.

33) Check for update provides no feedback unless an update is available.

34) Automatic reconnection with "Allow reconnection to interrupt resumable downloads" appears to work correctly now!

35) Still no stop a downloading link command.

36) Stopping all downloads (with the Stop toolbar button) takes a long time.

37) The toolbar buttons have not option to include text descriptions (which should be the default).

38) JD should consistently add Help as the first (or last) right click entry.

39) When a user is not present to provide a response for a Captcha challenge, the links is still marked as "Fatal Error" instead of "User Needed: Captcha", which should be retryable when JD knows the user has returned.

40) jdownloader -config crashes. It starts up, displays the configuration, and the crashes on click'n'load in the database. It then just sits there, not reading the keyboard. Anything typed will be sent to the shell after Ctrl+C.
jdownloader has this exception every time it starts. Normally, it is benign, but -config about:config does not work at alll.

Last edited by drbits; 06.04.2010 at 03:52.
  #3  
Old 08.04.2010, 13:28
remi
Guest
 
Posts: n/a
Default

drbits

I'm really impressed with this list. You are a busy bee. You're probably the best tester I've ever known.

You asked me to review 23).

Quote:
Originally Posted by drbits View Post
23) Not being able to sort on status makes large packages much harder to deal with.
23a) For example (probably not in this release):
finished (downloaded and extracted or hash checked): 100, (Green Check mark icon)
downloaded: 90, (Blue check mark)
downloading: 80, (Green down arrow)
negotiating download: 75, (displayed as downloading)
HTTP connecting: 70, (displayed as downloading)
waiting in the queue: 60, (nothing to display)
Unknown: not checked (and similar benign status, such as duplicate link): 50 (blue link)
in a wait that affects all links for a host: 45 (blue clock icon?)
retryable (if it has not retried yet): 40 (blue link), retries exhausted (example of resumable)
waiting for user (resumable): 30 (blue clock?)
user disabled link: 25 (shown by blue lock icon?)
Host busy (including no slots): 20 (orange clock icon)
Unexpected data: 15 (orange link?)
downloaded, but post-processing error: 10 (orange down arrow)
"bad link", Deleted (and other permanent errors): 5 (broken orange link)
I'll only review the statuses as I'm not interested in the icons. I refer to the State Diagram.

Here are my remarks.

We shouldn't mix Statuses and Status Messages (sub-states). I think "negotiating download" and "HTTP connecting" are examples of such sub-states. They belong to the "downloading" or "waiting" states. "Host busy" is an example of a "temporary error". It should be displayed as a Status Message and in a separate column.

With "Finished" you probably mean "extracted" and "joined". This is confusing, because you lost important information. Take the example of a split avi file. Customers might think that it is downloaded, but as long as it isn't joined it isn't finished. In addition, if the split files are in .rar archives, then they might have been extracted but not joined due to a disk space problem. Their status should be "extracted" and not "downloaded". The end states have a transition to the target state in the diagram.

"Unexpected data" is due to a bug in jD (host plug-in outdated) and is called a "jD bug".

Your "downloaded, but post-processing error" might be a special case of a "customer input error", meaning the customer should intervene and decide what needs to happen, but it might be a jD bug (missing transition in State Diagram) as well.

Everyone can see which states are missing by looking at the State Diagram. The transitions in the SD determine the order of the states.

In the "Linkgrabber Off/online" discussion I proposed three states :- found, deleted, and unknown. The deleted state is a sub-state of "permanent error". A "found" link becomes a "waiting" (in the download queue) or a "disabled" state.

"resumable" is not the same as Waiting for user if you mean "customer input error" with the latter.
  #4  
Old 08.04.2010, 20:21
drbits's Avatar
drbits drbits is offline
JD English Support (inactive)
 
Join Date: Sep 2009
Location: Physically in Los Angeles, CA, USA
Posts: 4,437
Default

a) I agree that I added some substates to the states list. That is why the icons are the same. I should edit that.
b) I think the statuses for extraction and join problems should not be different. If everything succeeds, then we need 1 state (thus Finished). If we have an extraction problem, then the file is still Downloaded, but we need a name for post processing error, because if we use 7zip to post process, most merging will be done by 7zip. We cannot always tell the difference between volumes and splits. Maybe this is "Downloaded: processing error (CRC)" or "Downloaded: processing error (password)" or "Downloaded: error volume ## missing".
c) It is not Plugin out of date or JD bug if a host changed behavior. The bug is that JD cannot automatically work around these problems. Downloading: error connecting. There are also real data errors. I am not sure what to call this, but we have to stop wording things to blame JD when a host changes.
d) For most common file types, we know the data type after reading just a few characters. That is how JD knows to try a password. If we have a signature and a known extension, JD can determine whether the password is correct by reading the signature again (it does not do this currently). So usually, we can distinguish the substates of processing errors. Some continue a cycle, some are Resumable (need customer aid), such as password needed or volume missing.
e) I thought I was consistent with Found, Deleted, and Unknown states. You are right that Found is the same as waiting in the queue. It is different from the Waiting state, which is waiting for the host (Waiting: host busy, Waiting: file busy, Waiting: quota exceeded). We need the Found status as part of the Linkgrabber processing. A file is not in the queue when it is in Linkgrabber.
f) I would like to consider Resumable to be "customer assistance needed". Whether there was a customer error is a substate issue. JD does not care whose fault it is, we give customers an infinite number of tries for file passwords, customers get to retry Captchas until host lock-out, and so on. If we have to create an icon for it, maybe it should be a stick figure person?
  #5  
Old 09.04.2010, 13:11
remi
Guest
 
Posts: n/a
Default

b) Yes, I know we disagree on that.

c) As long as we don't have an Artificially Intelligent jD, the resolution of those problems is manually correcting a host plug-in or some other code in jD. The customer needs to know that the program needs to be updated after the code has been changed by the developers. The forums to report these bugs are "General Bugreport" and "Hoster-Plugins" (Use this forum for bugreports concerning our hosterplugins). As they both refer to bugs, why wouldn't we accept this in jD's customer interface as well? If you find a better name for that state, please propose it.

e) The "found" state has a transition to the "waiting" state when the customer clicks on the "Continue with all" (BTW this is a very bad name for this function) button. The "waiting" state can have sub-states like "host busy", "captcha recognition busy", etc.

f) I would never talk about "customer error" but about "customer input needed". The "resumable" state can be reached when the customer stops the download or by exiting jD. I would restrict the definition of "customer input needed" to errors that need customer intervention. A download that has been stopped by the customer is not "in error".
  #6  
Old 10.04.2010, 10:43
drbits's Avatar
drbits drbits is offline
JD English Support (inactive)
 
Join Date: Sep 2009
Location: Physically in Los Angeles, CA, USA
Posts: 4,437
Default

b) Downloaded: extraction error -> Downloaded: error found and Downloaded: wrong password if we can distinguish them (if the signature can be extracted with the password, the CRC error is a Permanent error in the file and we can recommend re-download. If the password is wrong, it is customer input needed. There is also an oxymoron Downloaded: file missing (the package is does not contain the complete archive).

Downloaded: merging, Downloaded extracting, or or Downloaded: processing are fine.

c) I still think that telling the truth is better. Downloading: error: host has changed (plugin update needed) is better than Plugin error (out of date). The Plugin has not expired, the host has changed, so the plugin needs to be updated.

I really don't know. I would be more comfortable with Downloading error: host plugin needs update than Plugin error (out of date). This still is consistent with the board and is explicit about what needs to happen.

e) The Found state transitions to the Queued state. A link is Waiting if the hosts says to wait or the host is busy. We have to distinguish that from a link passively waiting to get to the front of the line (queue in UK). A Queued link is blocked by a Waiting link or a Downloading link (one link per Maximum Simultaneous download for that host).

We could change it to Downloading: waiting, but then calling the rest of the links Waiting is confusing. Besides, we should not show a status for links that are just queued, waiting their turn.

f) Agreed. Resumable is really closer to Retryable than to User input needed.
  #7  
Old 10.04.2010, 12:35
remi
Guest
 
Posts: n/a
Default

b) I get parsing errors in my brain when I read that. Can you please correct grammar and parentheses, because I don't understand it? I repeat that I agree that we still disagree on that issue. I hope with you that jD will ever attain that level of sophistication and the customer will not have to know anything about extraction and joining problems.

c) It's not about not telling the truth. You're referring to causes the customer has no business with. jD's main business goal is to shield the customer from these host sites' adverts and other crap.

e) The "queued" state is a super state of all the states in the diagram. All the links in the download queue are "queued". A link waiting to be download is in the "waiting" state, whatever the reason for the waiting. The reason for the waiting can be put in a Status Message. All links should have a status and it should be shown to the customer.
  #8  
Old 28.05.2010, 14:07
Greeny
Guest
 
Posts: n/a
Default

9a) If this option is enabled, the info panel automatically opens when a new filepackage is grabbed to the linkgrabber! this is the panel that opens, when you double click on a filepackge ...

15) Do you mean the balloon? Or is there a dialog?

16) fixed with my latest commit
  #9  
Old 28.05.2010, 21:49
drbits's Avatar
drbits drbits is offline
JD English Support (inactive)
 
Join Date: Sep 2009
Location: Physically in Los Angeles, CA, USA
Posts: 4,437
Default

@ Greeny,
15) It appears as a balloon. I believe this is a dialog.
16) Thank you!

@ Remi,
Sorry to get back to you so late, I missed your message.
b) I was trying to say that we should somehow distinguish between a CRC error in a volume (needs to be redownloaded) and a bad password (all files have CRC errors, but the volumes do not)
c) Plugin out of date means that there is a problem with JD. Host has changed means that JD cannot yet work with the changed host. The effect is the same, the team has to update the plugin. It is a matter of blame in the minds of the users. Nobody did something wrong, but Plugin out of date makes it appear that the JD team did something wrong or did not act before a known date.
e) It is confusing to have any status display associated with links that are just waiting for their turn. There is no error, success, or user action involved.

This is especially true of the "Waiting for new IP". That message is a menace (see bugtracker issue .

Last edited by drbits; 28.05.2010 at 23:37.
  #10  
Old 29.05.2010, 03:36
Greeny
Guest
 
Posts: n/a
Default

Quote:
Originally Posted by drbits View Post
@ Greeny,
15) It appears as a balloon. I believe this is a dialog.
I'm sorry to say it, but with our current balloon/dialog system its not possible to let a "Dont show again" checkbox being displayed in a balloon... this is currently only possible in the dialogs...
  #11  
Old 29.05.2010, 04:03
drbits's Avatar
drbits drbits is offline
JD English Support (inactive)
 
Join Date: Sep 2009
Location: Physically in Los Angeles, CA, USA
Posts: 4,437
Default

That is understandable. One problem with that specific balloon is that there does not appear to be enough vertical space in the box (or the second line is a much smaller font and it only feels that way).
  #12  
Old 29.05.2010, 11:16
remi
Guest
 
Posts: n/a
Cool

Quote:
Originally Posted by drbits View Post
e) It is confusing to have any status display associated with links that are just waiting for their turn. There is no error, success, or user action involved.
"waiting" is better than "queued". I agree that "Waiting for new IP" doesn't make any sense for people who have a static IP address or want to stay connected all the time.
 

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT +2. The time now is 17:54.
Provided By AppWork GmbH | Privacy | Imprint
Parts of the Design are used from Kirsch designed by Andrew & Austin
Powered by vBulletin® Version 3.8.10 Beta 1
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.