Discuz! NT running in 64-bit windows

Http://www.blogwind.com/Wuvist/74545.shtml

==========================================

Very Involved. wait a year for discuz! The free version of NT still does not support 64-bit windows.

The official guide for 64-bit Windows support is to ask users to set IIS to a 32-bit compatible mode... If you say it is not said, It is not called running discuz in 64-bit windows! NT, this is how to run discuz without using a 64-bit environment! NT...

(The most depressing thing is whether to enable 32-bit support for IIS 6 is a global setting. I have dedicated 32-bit support for the Forum. What should I do if other 64-bit Programs depend on the server ?)

I have consulted discuz's customer service directly. mm is very polite and has a good attitude. However, the solution is to allow me to purchase commercial licenses and say that it is okay to pay for it.

But I was so upset... With my own development experience, discuz! The 64-bit running failure of NT directly crashes the IIS application pool, which must be a problem in the program... Instead of authorization issues...

I am always afraid of being fooled by mm... 3000 Yuan... Discuz! NT is open source... Isn't it better to earn the 3000 yuan for yourself?

In this world, it will not always be the only problem I encountered... I'm crazy... Wait almost a year... Still not solved...

Today, I finally got angry... Do it yourself...

First, download discuz! NT Source: https://svn.51aspx.com/svn/dnt

Very strange, discuz! NT does not need Google Code or the like; 51aspx download is slow to death...

Locally compile, upload, and deploy the debug version... We can see from the official forum that some netizens say they want to compile the 64-bit version, and even say they want to compile discuz! Several dependent libraries used by NT are also re-compiled in 64-bit format... I doubt whether these netizens have tried it... Anyway, I did what they said... If you waste a whole day without saying it, it never works...

Finally, the debug diagnostic tool (thanks to the motherland, Microsoft finally launched the 64 bit version at the end of last year !) Artifacts...

Use the default crash rule to track the application pool process of the Forum... Access an empty ASPX page to start the process, and then access the Forum homepage... Sure enough... While debug diagnostic tools automatically dump the process...

Very good... Continue offering the debugging tools for Windows artifacts...

Load Dump File... Run :! Analyze-V

Hey... Display now:

 

2017000003502a90 00000642788f2237 mscorlib_ni! System. accessviolationexception .. ctor () + 0x17

(Transitionum)

(Transitionmu)

201700000354e6d0 0000064278acb013 mscorlib_ni! System. Security. cryptography. cryptoapitransform. transformfinalblock (byte [], int32, int32) + 0x123

201700000354e760 0000064278334403 mscorlib_ni! System. Security. cryptography. cryptostream. flushfinalblock () + 0x33

201700000354e7a0 00000642801d09ba discuz_common! Discuz. Common. Des. Decode (system. String, system. String) + 0x11a

000000000354e810 00000642801d0430 discuz_forum! Discuz. Forum. onlineusers. updateinfo (system. String, int32, int32, system. String) + 0xc0

000000000354e890 00000642801ce4ab discuz_forum! Discuz. Forum. pagebase .. ctor () + 0x55b

The problem is obvious... Discuz! An error occurred while checking the user information code when nt started... Specifically:
The 97-line des class decode function of the discuz. Common \ Encrypt. CS file...

Not familiar with DES. It is unclear why flushfinalblock runs in 64-Bit mode... Implement deCODE/encode function of des again... Upload server... The Forum homepage has finally come out...

Burst into tears...