Jump to content
  • 0

Install Problem


Question

Posted

Hi there , I wanted to start a Freya server  so that i can test some stuff and I've downloaded l2j server's latest compiled revision  and I've also downloaded Navicat and MySQL. I installed MySQL and Navicat and followed the l2j guides on how to install DP,LS and GS but when I try to run the database_installer i get this error.

 

 

sdsyi.png

 

 

Any help will be appreciated.

8 answers to this question

Recommended Posts

  • 0
Posted

Have you put path for your db at mysql?

 

EX

Lets take a look the properties from DB Installer

[table][tr][td]@echo off

TITLE L2 Phoenix Setup

REM ######################################## Automatic updater for L2 Phoenix - Do not edit !!!

goto answer%ERRORLEVEL%

:answerTrue

set fastend=yes

goto upgrade_db

:answer0

set fastend=no

 

set user=(your mysql username[defult as (root)])

set pass=(your mysql password)

set DBname=[glow=red,2,300]l2pdb[/glow] <-----Your path name from mysql (added with navicat to mysql)

set DBHost=localhost

 

set Generaltables=accounts augmentations clanhall gameservers banned_ips loginserv_log character_friends character_hennas character_macroses character_quests character_recipebook character_shortcuts character_skills character_effects_save character_skills_save character_subclasses characters character_variables clanhall_bids clanhall_data clan_data clanhall_decorations_bids ally_data clan_wars items pets server_variables seven_signs seven_signs_festival siege_clans killcount dropcount craftcount game_log petitions seven_signs_status global_tasks raidboss_status manor_crop manor_seeds

set Ignore=--ignore-table=%DBname%.game_log --ignore-table=%DBname%.loginserv_log --ignore-table=%DBname%.petitions

 

REM ####################################[/table]

  • 0
Posted

:configure

call :colors 17

title L2JDP installer - Setup

cls

set config_version=2

if NOT %upgrade_mode% == 2 (

set fresh_setup=1

set mysqlBinPath=C:\Program Files\MySQL\MySQL Server 5.1\bin

set lsuser=root

set lspass=root

set lsdb=l2jdb

set lshost=localhost

set cbuser=root

set cbpass=root

set cbdb=l2jdb

set cbhost=localhost

set gsuser=root

set gspass=root

set gsdb=l2jdb

set gshost=localhost

set cmode=c

set backup=.

set logdir=.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
    • If the problem is that the target is lost, the action of aiming at another character, upon losing collision, does not allow aiming.   This one works as it should, allowing you to target characters
    • MICROTEXT AND WATERMARKS BREAK MOST RENDERINGS Microtext and watermarks aren’t just small decorative details. They are one of the most common reasons a document fails verification, even when it looks decent at first glance. The issue is that these elements are almost impossible to reproduce “by eye.” Microtext requires precise geometry and legibility at a very small size, while a watermark needs the correct density, transparency, and accurate placement relative to other security features. Any deviation becomes obvious during detailed inspection. ▪ What’s most often done wrong: - microtext is drawn too thick or blurry - the watermark is made either too visible or almost invisible - the positioning between microtext and watermark is ignored - the original printing technology isn’t taken into account when choosing density and shape - The stronger the document’s security features, the less room there is for approximation. What matters here isn’t visual similarity, but accurate reproduction of the original technical characteristics. If your document contains microtext and watermarks, this is always an area that requires extra attention. Write to us in DMs. We’ll review your case and point out exactly which details need the highest precision during rendering. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #microtext #photoshop #editing #watermarks
    • GoldRush launches tomorrow! July 18 16:00 GMT+3 Europe / International Register your account in the website, connect wallet and be ready to dominate!
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..