Newbie Spellweaver
- Joined
- Mar 24, 2016
- Messages
- 12
- Reaction score
- 7
Without the resources, there won't be much you can do with it.
Hey your latest commit has viruses in it. Not sure if you attempted to do this intentionally or you were unaware your system is infected, you should check it out ASAP.
You must be registered to see links
yeah, currently i'm working on an virtual system windows, so i'm not care too much about virus (just now).Hey your latest commit has viruses in it. Not sure if you attempted to do this intentionally or you were unaware your system is infected, you should check it out ASAP.
You must be registered to see links
yeah, currently i'm working on an virtual system windows, so i'm not care too much about virus (just now).
these built lib all are from the source code (not found any where, so i use them directly), i'm only trying to build it to run-able, then I will re-check these built binary after
Hmmm, okay. You should try to be aware of what you put out there though, as others will probably want to use what you commit and can potentially be infected unwittingly. Also, its a general rule of thumb to NOT version control built binaries unless its in a seperate repo or something. Just keeps the repo clean and can prevent situations like this where your system was infected unknowingly and you commit infected files.yeah, currently i'm working on an virtual system windows, so i'm not care too much about virus (just now).
these built lib all are from the source code (not found any where, so i use them directly), i'm only trying to build it to run-able, then I will re-check these built binary after
Thanks for your suggest, I 'll create a new VM to work and follow these stepYou must be registered to see links
Again, Ramnit is highly infectious so you should not be knowingly releasing it. Doing so is irresponsible.
Create a git patch of what you have done (You must be registered to see links) and re-apply it to the source code to ensure there is no infection.
You should honestly just trash the VM, and start a new one and work from that.
Hmmm, okay. You should try to be aware of what you put out there though, as others will probably want to use what you commit and can potentially be infected unwittingly. Also, its a general rule of thumb to NOT version control built binaries unless its in a seperate repo or something. Just keeps the repo clean and can prevent situations like this where your system was infected unknowingly and you commit infected files.
》》》》Unzip the jx3Server folder to the root directory of the D drive! ""
1. Start APM, click on "Start APMServ" below, and see "MySQL5.1 is started" after the next step. If MySQL 5.1 does not start successfully, follow the prompts and try again.
2.2. Start SO3GameCenterD
3 .3. Start SO3GatewayD
4.4. Start SO3GameServerD
Although there are many tips in the interface, Failed...
Find JX3ClientD.exe in the client folder and double click to start
Test account root password 123456
Baidu disk file description:
The "Related Information" folder is only available for those who need vs2005 and research source code.
Thanks marelegg so much for your searching
I'm uploading it to:You must be registered to see links
will extract the source code and upload to github soon to develop it
www.523play.com
Glad to see work being done on this.
UPDATE:
When you extract the multi-part files JX3 - Client server.part1.7z and JX3 - Client server.part2.7z, the
archive 剑侠情缘3单机版一键服务端+架设工具整理+配套客户端+教程+源码.rar is password encrypted.
Always let people know the password in a release if there is one.
PASWORD:Code:www.523play.com