Age Verification
This website contains age-restricted material including nudity and explicit content. By entering, you confirm being at least 18 years old or the age of majority in the jurisdiction you are accessing the website from.
I am 18+ or older - Enter
I am under 18 - Exit
Our parental controls page explains how you can easily block access to this site.

Ostatnie posty - Strona 727

  Forum

ComteDracula
Dołączył: Aug 2017
2847 post(y/ów)

UPDATED! PLEASE READ - Q&A Crazy week Season 3

Wszystko o iStripper
September 19, 2020, 110 odpowiedzi
Merci @Philours pour l'info.

J'ai décidé de participer, malgré mon aversion pour les jeux de hasard, vu qu'il y avait un chemin prédéfini pour obtenir la carte de Cara mell (qui est l'une de mes favorites).

Pour ma part, je ne pouvais jouer qu'aux cartes à gratter, ayant toutes les cartes.

J'ai acheté 35 cartes à gratter à 20 crédits chacun, pour un total de 700 crédits.

J'ai gagné 780 crédits. (14x20 crédits + 3x100 crédits + 1x200 crédits)

Donc gain de 80 crédits + l'obtention de la carte de Cara Mell, qui s'est avérée dans mon cas gratuite.

Heureusement, j'ai été chanceux, mais je constate comment il est facile une fois dans ce genre de jeux de participer plusieurs fois, et aussi de perdre facilement des crédits, lorsqu'on est malchanceux. Il faut vraiment que quelqu'un se mette une limite pour cesser de participer. Dans mon cas ici c'était facile, puisque mon objectif était d'avoir la carte de Cara Mell et cesser par la suite.

Le pire est de continuer à jouer lorsqu'on a eu des gains et ainsi les dépenser inutilement, et même de perdre encore plus en poursuivant, dans l'espoir d'obtenir les autres cartes SEC par exemple.


Thanks @Philours for the info.

I decided to participate, despite my aversion to gambling, since there was a predefined path to get Cara Mell's card (who is one of my favorites).

For my part, I could only play scratch cards, having all the cards.

I bought 35 scratch cards at 20 credits each, for a total of 700 credits.

I won 780 credits. (14x20 credits + 3x100 credits + 1x200 credits)

So gain 80 credits + obtaining the Cara Mell card, which in my case turned out to be free.

Fortunately, I was lucky, but I see how easy it is once in these kinds of games to participate several times, and also easily lose credits, when you are unlucky. Someone really has to set a limit to stop participating. In my case here it was easy, since my goal was to have Cara Mell's card and quit afterwards.

The worst is to continue playing when you have had winnings and thus spend them unnecessarily, and even to lose even more by continuing, in the hope of obtaining the other SEC cards for example.
TheEmu
Dołączył: Jul 2012
7424 post(y/ów)

Moving iStripper data to a new location

Wszystko o iStripper
September 18, 2020, 35 odpowiedzi
No @Hansachs they are not entirely different - I have ***** from helpful "knowledgable" users at both ends of the scale. In one case one such user changed the value of an environment variable (actually a VMS Logical Name) that provided the location of just such a directory. It "worked" in that it did what he wanted, in the short term, but caused that same user problems later when he used some other feature of the program that relied on the relationship between that directory and others. This is an exact equivalent to the case of changing the registry entry pointing to a directory.

No matter how "knowledgeable" we are we can not know if

1) There is some part of the program that has used knowledge of where the data directory is either directly by hard coding some or all of its name or uses knowledge of the relative paths between the data directory and some other directory such as the vghd or vghd/bin directories. I very much doubt that there are any such usages, but we do not know that there are none. (One possibility is in some old, little used part of the program that may only get used for debugging purposes)

2) That the meaning, or even the existence, of the registry entry will not change with a future release or that some feature introduces the situation described in the previous paragraph.

3) We do not know if it is "safe" to change the directory to some arbitrary name. For example the software may use a fixed size buffer somewhere to hold the data directory name. What happens if the user provides an a very long path name that causes the buffer to overflow?

4) We do not know if it is safe to change the directory name while the program is running. Perhaps different parts of the software handle it in different ways. For example one part may read the directory path from the registry during program initialisation and from then on use that value until the program exits but some other part reads it only when some particular function is first used and some other part re-reads it every time some other function is used. This would lead to different parts of the program using different locations for the data directory. Given that the program now seems to use rather more threads than it did previously such behaviour could well have been introduced quite recently.

The last could be particularly problematic if a naive user was following instructions even if they are told to exit the program before editing the registry. It has been quite obvious from previous posts that many user are not aware that closing the GUI does not quit the program even if there are no visible signs of it on the desktop.

Now, I do not think that any of these are particularly likely for the particular case under discussion, but we simply do not know.

Having spent far too much of my working life sorting out problems such as the above (and I have seen case similar to all of those that I have outlined) I am very disappointed when others suggest that doing such things, no matter how simple or obviously "correct" they are, are not a problem. They all too often have unforseen, and sometimes expensive, side effects that in the worst case only show up intermitently several months later.