Current Policy on the old win32asm forum

[hutch--]

It would seem that even after demonstrating goodwill by removing a number of postings in the masm forum so that negotiations could be carried out in pressure free environment, the serious concerns in terms of legality issues in the old win32asm forum will not be met and the administration of that forum will continue to try and cover up its own policy changes on illegal matters by trying to shift the focus to the masm32 project.

After having worked for many years in conjunction with many other programmer to bring assembler programming back into mainstream programming, I am not willing to see these advances put at risk because the membership of the old win32asm forum has collapsed under the weight of neglect and poor management and its administration starting to scrape the barrel to maintain membership by trying to associate assembler programming with the sewerage that it was rescued from about 10 years ago.

Legality of content can never be a negotiable matter and as long as the newly written forum rule of the win32asm forum have an obvious loophole that allows cracking under the guise of reverse engineering, it endangers the work done by so many people over a long period of time which is simply unacceptable.  :naughty:

I make it clear that I have no criticism whatsoever for the majority of the moderators in the win32asm forum as I see them as high integrity and highly experienced programmers who are capable of running a forum of this type in a very efficient and professional manner. The problem is wholly and solely one of its administration not being competent to do the job. There is simply more to running a successful forum that having an account on a server and being in control of the server side software that the forum uses.

Forums are about people, not control issues modelled after IRC style takeovers and this has directly effected the running of the old win32asm forum for some years. With the loss in short succession of both the MASM32 project and FASM, the old win32asm forum ran out of puff technically and has floundered ever since while being infiltrated by virus programmers as the wheels fell off.

As it is apparent that the current administration will not make the changes necessary to protect its members and run the forum in a competent manner, I will not recommend that any person associate with that forum until the administration is passed to the team of moderators that have the integrity and experience to do the job properly and rebuild the old win32asm forum back into the premium venue that it used to be.

[hutch--]

On the issue of "yet another attempt to undermine the MASM32 Project" the proof of the fallacy has already been published by the Administrator of the old win32asm forum in the following form.

I did attempt to make contact with Microsoft myself,
but so far they have only responded with content that
is of the same clarity of hutch's history of reasoning,
and statements about his supposed legal contract.

The sum total weight of the accusations made by the administrator of the win32asm forum is addressed in his own posting where he simply did not get the answer from Microsoft that he wanted and even in the clear knowledge that he is wrong in his accusations, he has persisted in trying to use criticism of the Microsoft EULA as a means of covering up the serious legal problems that he has introduced into the old win32asm forum by writing a blatant loophole into the rules that provide a justification for cracking under the guise of "reverse engineering".

The administrator of the old win32asm forum has demonstrated that he is not capable of negotiating to solve the legal problem he has introduced so there is no alternative than to call for his resignation from the administration of the old win32asm forum so that control of that forum is passed to the team of moderators who have both the integrity and expertise to rebuild it back into the premium venue it used to be some years ago.

[hutch--]

Why have these 4 year old links been left here ?

Find out why at the following URL.

http://assemblercode.com/kanios/