应《网络安全法》要求，自2017年10月1日起，未进行实名认证将不得使用互联网跟帖服务。为保障您的帐号能够正常使用，请尽快对帐号进行手机号验证，感谢您的理解与支持！

24小时热门版块排行榜    

小木虫论坛-学术科研互动平台 » 计算模拟区 » 第一性原理 » 在线答疑:Wien2k的问题
526/1返回列表
查看: 11094  |  回复: 274
只看楼主 @他人 存档 新回复提醒 (忽略) 收藏    在APP中查看
当前主题已经存档。
当前只显示满足指定条件的回帖，点击这里查看本话题的所有回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主

[交流] 在线答疑:Wien2k的问题

希望能在这里跟大家一起交流探讨涉及Wien2k的问题。
希望做Wien2k的朋友有什么建议、资料或信息能在 这里提供出来，以便交流！
以下内容随时补充~~~~


群名：小木虫wien2k群
群号码：51109254

群名：小木虫 Wien2k(二）
群号码：75403996



欢迎提问，提问有奖。
更欢迎高手们前来解答问题，合理的答案有重奖！
谢谢！

[ Last edited by wuli8 on 2009-11-10 at 16:41 ]
回复此楼

» 猜你喜欢
…………
1楼 2008-12-01 21:19:07
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主
★ ★
qasd(金币+2,VIP+0):xiexie~ 8-12 15:03
Cohesive energies
Problem: The cohesive energy of compounds with heavier elements is positive.
Analysis:
Lstart is a fully relativistic atomic code and thus provides a better (and thus lower) total energy than the LAPW calculations, which have only a scalar relativistic basis (even when SO is added a posteriori).
Fix:
Starting for second-row elements (this depends a little on the required accuracy) you must calculate the atomic energy not with LSTART, but with LAPW. Create a FCC box with lattice constants of about 30 bohr and your atom at (0,0,0). Use identical RMT, RKMAX, but only 1 k-point and spinpolarization (for non-closed shell atoms).
Some atoms (with partly occupied orbitals or in particular transition metal atoms, where the occupation flips between a 4s and 3d states) may be difficult to converge. Use a broadening method (e.g. TEMP 0.005) to get equal partial occupations and thus a stable solution.

WIEN2k-FAQ: Explanations on EFGs (EFG switch in case.in2)

Problem: The switch EFG in case.in2 produces an output, which can be used to analyse the different contributions to the EFG. However, it is not documented and not easy to understand.




WIEN2k-FAQ: DOS is calculated only up to a certain (low) energy

For some cases, the standard inputs provide a DOS only for energies close to EF, but not for higher energies, even when you specify a large E-range in case.int. The reason for that is, that the DOS is truncated at the lowest energy of the last fully available band in order to avoid plotting of an incomplete DOS. The solution is:
1. Edit case.in1 and increase the energy range: Increase E-max from 1.5 to a larger value (e.g. 2.5 or more).
2. Rerun "x lapw1" (lapw1c) and "x lapw2 -qtl" (lapw2c). This produces a case.qtl file with more bands.
3. Rerun tetra.


WIEN2k-FAQ: The SCF cycle fails after a few iterations

In cases with larger unit cells and various atoms with more or less localized electronic states it can happen, that the scf cycle fails in the second (or after a few more) iteration. Possible error messages include:
1. QTL-B value .gt. XXX in LAPW2
2. Could not find E-TOP/E-Bottom in LAPW1
Usually in such cases the mixing factor in MIXER was too large and too large charge fluctuations occured (You may see this using 'grep IS case.scf' or 'grep :NTOxx case.scf'). In such a case
1. remove the broyden and the scf files (rm *.broy* case.scf)
2. generate a new starting density (x dstart (-c/-up/-dn))
3. reduce the mixing parameter from 0.4 to e.g. 0.1 in case.inm (sometimes even 0.01 and/or a change to PRATT-mixing for some iterations may be necessary. Note: final convergence should always be reached using BROYD-mixing)
4. and restart the scf cycle (run_lapw or runsp_lapw).

Another possibility is that EF got quite large (usually this happens for heavy elements (actinides); check using grep :FER case.scf). Then the default E-parameters (0.30 Ry) in case.in1 are no longer a good choice because some LO-energies could be in the same range, which results in ghostbands.
Check in case.scf1 whether or not a "searched" energy and a fixed one got too close like:
OVERALL ENERGY PARAMETER IS 0.3000
E( 1)= 0.3000
E( 1)= 0.2875 E(BOTTOM)= 0.395 E(TOP)= 0.180
In such cases increase the default 0.30 to something close to EF, or fix the energy parameters without search (case.in1).


WIEN2k-FAQ: Charged cells

"Charged" cells will most likely require the construction of supercells, (see the faq on creating supercells) and this hole discussion targets charged impurities, vacancies,....
• Setup your supercell, put impurities, vacancies,.. (all with neutral atoms!)
• Run a standard initialization (init_lapw) with NEUTRAL atoms. Don't fiddle around with case.inst (positively charged atoms may work (and one can neglect the warnings "NUMBER OF ELECTRONS NE IZ ", but most negative ions are unstable in DFT and will not work.
• run_lapw (again for neutral atoms !) . Save the results using "save_lapw case_neutral"
• Edit case.in2: In the second line you see the number of electrons NE. Add or remove an electron to get the desired charged state.
• Edit case.inm: The first line must read:
• BROYD 1.0 YES (when you added an electron at step 4 or
• BROYD -1.0 YES (when you removed an electron at step 4
The position of "YES" is important!!! When reading characters in Fortran one must use a fixed format (or put characters into quotes).
• run_lapw
• I NEVER run init_lapw again!!! Usually init_lapw should be run only ONCE in a directory, because any changes which would require rerunning init_lapw (symmetry changes,....) should be done in a fresh "case"


WIEN2k-FAQ: Construction of supercells

For most (simple) supercells you can start with the regular case.struct file and use "supercell" to generate the supercell-struct file.
However, when you construct supercells, it is usually NOT possible just to double the cells and leave all atoms at their ideal and equivalent positions. This would lead to large multiplicities (e.g. in big supercells even more than 48 atoms could be "equivalent" and of course there is NO SPACEGROUP corresponding to this type of cell, since they all can be reduced by translation symmetry.
So during setup, you have at lest to:
• displace (at least one) atoms, or
• change one of the atoms to a different type (usually you do supercells for impurities,... so put the impurity into the cell), or
• set at least for one atom-name a special label (A label means an name like "Cr1", "Cr2" or "O 4", where in the 3rd position is a number. This indicates to WIEN2k that these atoms should be non-equivalent.).
Then run init_lapw
• nn and sgroup determine which atoms are still equivalent (if nn does not agree with sgroup in the first place, you may have to "label" non-equivalent atoms (see above). If you now rerun nn, you may get another (better) list of non-equivalent positions.
• symmetry: determines proper symmetry operations and rot.matrices,...
• Check if your case.inst file is still valid (when the number of non-equivalent atoms has changed, probably not). Generate a proper case.inst file (either using "instgen_lapw" or "Structgen of W2web" and rerun init_lapw.
Note, that WIEN always preserves symmetry. So when you want to allow certain relaxations around an impurity, it might be necessary to displace some atoms by hand to break the high symmetry and allow such relaxations.


WIEN2k-FAQ: Positive Fermi energy: What does it mean ?

Eigenvalues, core states, linearization energies, the Fermi energy,... are given in Rydberg units in wien2k, and are relative to a zero-point that is defined as the average of the potential in the interstitial region. This is an arbitrary choice (one half of this average, or 2.6128 times this average would have been good as well). Therefore, it might happen that for some compounds (solids) your Fermi energy (:FER) is positive, while for others (surfaces or molecules with lots of vacuum) it is negative. This has no physical meaning, and it is also not an indication of a possible error, it is just due to the choice of the zero-point.
Why is there a need to make such a choice? For a free atom, the choice of zero is arbitrary as well, but if one makes the usual convention that the potential at infinity is zero, then negative and positive energies indicate bound and unbound states, respectively. This is intuitively appealing. But for solids, there is nothing special about infinity: the solid is everywhere, also at infinity. Therefore, another convention has to be made, like the one explained above.
Please note, the TOTAL-Energy does NOT depend on this choice!!!)


--------------------------------------------------------------------------------

Cohesive energies
Problem: The cohesive energy of compounds with heavier elements is positive.
Analysis:
Lstart is a fully relativistic atomic code and thus provides a better (and thus lower) total energy than the LAPW calculations, which have only a scalar relativistic basis (even when SO is added a posteriori).
Fix:
Starting for second-row elements (this depends a little on the required accuracy) you must calculate the atomic energy not with LSTART, but with LAPW. Create a FCC box with lattice constants of about 30 bohr and your atom at (0,0,0). Use identical RMT, RKMAX, but only 1 k-point and spinpolarization (for non-closed shell atoms).
Some atoms (with partly occupied orbitals or in particular transition metal atoms, where the occupation flips between a 4s and 3d states) may be difficult to converge. Use a broadening method (e.g. TEMP 0.005) to get equal partial occupations and thus a stable solution.

WIEN2k-FAQ: Explanations on EFGs (EFG switch in case.in2)

Problem: The switch EFG in case.in2 produces an output, which can be used to analyse the different contributions to the EFG. However, it is not documented and not easy to understand.


WIEN2k-FAQ: Setup of antiferromagnetic calculations?

Setup of antiferromagnetic calculations requires some tricks which will be described below:
1. You need to construct a unit cell which allows for the desired AF ordering. E.g. for bcc Cr you have to put "P" lattice and 2 NON-equivalent atoms at (0,0,0) and (0.5,0.5,0.5). In order to make nn working properly, you should also specify different labels in the "name(3:10)"-field for the two AF-atoms (Eg. "Cr1" and "Cr2".
2. Run init_lapw. nn and/or sgroup determines equivalent atoms. Accept eventually the new struct_nn file (You may have to use the same procedure as described in faq:supercells).
3. Edit case.inst and flip the spin of the second AF atom. This means you must invert the spin-up and dn occupation of this atom. Atoms which carry no spin (e.g. an O between two AF metal atoms) should be made non-spinpolarized by setting equal numbers of up and dn-electrons.
For AFM NiO case.inst looks like:
4. Ni
5. Ar 3 5
6. 3, 2,2.0 N
7. 3, 2,2.0 N
8. 3,-3,3.0 N
9. 3,-3,1.0 N
10. 4,-1,1.0 N
11. 4,-1,1.0 N
12. Ni
13. Ar 3 5
14. 3, 2,2.0 N
15. 3, 2,2.0 N
16. 3,-3,1.0 N <=== spin flipped
17. 3,-3,3.0 N <=== spin flipped
18. 4,-1,1.0 N
19. 4,-1,1.0 N
20. O
21. He 3 5
22. 2,-1,1.0 N
23. 2,-1,1.0 N
24. 2, 1,1.0 N
25. 2, 1,1.0 N
26. 2,-2,1.0 N <=== equal occup for up/dn
27. 2,-2,1.0 N <=== equal occup for up/dn
28. **** End of Input
29. **** End of Input
30. Continue with init_lapw (rerunning lstart)
31. You may try to select "AFM-calculations", generate "case.inclmcopy" and use "runafm_lapw". For simplest use of "afminput" you should provide the nonmagnetic (or ferromagnetic) supergroup in "case.struct_supergroup". Please read the usersguide for more details. (help_lapw and search for AFM).
Since these programs are quite new and little tested, I recommend to check the final results of "runafm_lapw" by
32. "runsp_lapw". If the charge distance (grep IS case.scf) remains small and the magnetic moments do not change, runafm_lapw was successful, otherwise continue with runsp_lapw until convergence.


WIEN2k-FAQ: DOS is calculated only up to a certain (low) energy

For some cases, the standard inputs provide a DOS only for energies close to EF, but not for higher energies, even when you specify a large E-range in case.int. The reason for that is, that the DOS is truncated at the lowest energy of the last fully available band in order to avoid plotting of an incomplete DOS. The solution is:
1. Edit case.in1 and increase the energy range: Increase E-max from 1.5 to a larger value (e.g. 2.5 or more).
2. Rerun "x lapw1" (lapw1c) and "x lapw2 -qtl" (lapw2c). This produces a case.qtl file with more bands.
3. Rerun tetra.


WIEN2k-FAQ: The SCF cycle fails after a few iterations

In cases with larger unit cells and various atoms with more or less localized electronic states it can happen, that the scf cycle fails in the second (or after a few more) iteration. Possible error messages include:
1. QTL-B value .gt. XXX in LAPW2
2. Could not find E-TOP/E-Bottom in LAPW1
Usually in such cases the mixing factor in MIXER was too large and too large charge fluctuations occured (You may see this using 'grep IS case.scf' or 'grep :NTOxx case.scf'). In such a case
1. remove the broyden and the scf files (rm *.broy* case.scf)
2. generate a new starting density (x dstart (-c/-up/-dn))
3. reduce the mixing parameter from 0.4 to e.g. 0.1 in case.inm (sometimes even 0.01 and/or a change to PRATT-mixing for some iterations may be necessary. Note: final convergence should always be reached using BROYD-mixing)
4. and restart the scf cycle (run_lapw or runsp_lapw).

Another possibility is that EF got quite large (usually this happens for heavy elements (actinides); check using grep :FER case.scf). Then the default E-parameters (0.30 Ry) in case.in1 are no longer a good choice because some LO-energies could be in the same range, which results in ghostbands.
Check in case.scf1 whether or not a "searched" energy and a fixed one got too close like:
OVERALL ENERGY PARAMETER IS 0.3000
E( 1)= 0.3000
E( 1)= 0.2875 E(BOTTOM)= 0.395 E(TOP)= 0.180
In such cases increase the default 0.30 to something close to EF, or fix the energy parameters without search (case.in1).


WIEN2k-FAQ: Charged cells

"Charged" cells will most likely require the construction of supercells, (see the faq on creating supercells) and this hole discussion targets charged impurities, vacancies,....
• Setup your supercell, put impurities, vacancies,.. (all with neutral atoms!)
• Run a standard initialization (init_lapw) with NEUTRAL atoms. Don't fiddle around with case.inst (positively charged atoms may work (and one can neglect the warnings "NUMBER OF ELECTRONS NE IZ ", but most negative ions are unstable in DFT and will not work.
• run_lapw (again for neutral atoms !) . Save the results using "save_lapw case_neutral"
• Edit case.in2: In the second line you see the number of electrons NE. Add or remove an electron to get the desired charged state.
• Edit case.inm: The first line must read:
• BROYD 1.0 YES (when you added an electron at step 4 or
• BROYD -1.0 YES (when you removed an electron at step 4
The position of "YES" is important!!! When reading characters in Fortran one must use a fixed format (or put characters into quotes).
• run_lapw
• I NEVER run init_lapw again!!! Usually init_lapw should be run only ONCE in a directory, because any changes which would require rerunning init_lapw (symmetry changes,....) should be done in a fresh "case"


WIEN2k-FAQ: Construction of supercells

For most (simple) supercells you can start with the regular case.struct file and use "supercell" to generate the supercell-struct file.
However, when you construct supercells, it is usually NOT possible just to double the cells and leave all atoms at their ideal and equivalent positions. This would lead to large multiplicities (e.g. in big supercells even more than 48 atoms could be "equivalent" and of course there is NO SPACEGROUP corresponding to this type of cell, since they all can be reduced by translation symmetry.
So during setup, you have at lest to:
• displace (at least one) atoms, or
• change one of the atoms to a different type (usually you do supercells for impurities,... so put the impurity into the cell), or
• set at least for one atom-name a special label (A label means an name like "Cr1", "Cr2" or "O 4", where in the 3rd position is a number. This indicates to WIEN2k that these atoms should be non-equivalent.).
Then run init_lapw
• nn and sgroup determine which atoms are still equivalent (if nn does not agree with sgroup in the first place, you may have to "label" non-equivalent atoms (see above). If you now rerun nn, you may get another (better) list of non-equivalent positions.
• symmetry: determines proper symmetry operations and rot.matrices,...
• Check if your case.inst file is still valid (when the number of non-equivalent atoms has changed, probably not). Generate a proper case.inst file (either using "instgen_lapw" or "Structgen of W2web" and rerun init_lapw.
Note, that WIEN always preserves symmetry. So when you want to allow certain relaxations around an impurity, it might be necessary to displace some atoms by hand to break the high symmetry and allow such relaxations.


WIEN2k-FAQ: Positive Fermi energy: What does it mean ?

Eigenvalues, core states, linearization energies, the Fermi energy,... are given in Rydberg units in wien2k, and are relative to a zero-point that is defined as the average of the potential in the interstitial region. This is an arbitrary choice (one half of this average, or 2.6128 times this average would have been good as well). Therefore, it might happen that for some compounds (solids) your Fermi energy (:FER) is positive, while for others (surfaces or molecules with lots of vacuum) it is negative. This has no physical meaning, and it is also not an indication of a possible error, it is just due to the choice of the zero-point.
Why is there a need to make such a choice? For a free atom, the choice of zero is arbitrary as well, but if one makes the usual convention that the potential at infinity is zero, then negative and positive energies indicate bound and unbound states, respectively. This is intuitively appealing. But for solids, there is nothing special about infinity: the solid is everywhere, also at infinity. Therefore, another convention has to be made, like the one explained above.
Please note, the TOTAL-Energy does NOT depend on this choice!!!)

[ Last edited by wuli8 on 2009-8-9 at 13:30 ]
赞一下(10人) 回复此楼
…………
256楼2009-08-09 13:28:39
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖
查看全部 275 个回答

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主
编译时出现如下问题，请问如何解决？
谢谢！
Compile time errors (if any) were:
SRC_afminput/compile.msg:make: *** [afminput.o] Error 127
SRC_aim/compile.msg:make[1]: *** [moduls.o] Error 127
SRC_aim/compile.msg:make: *** [real] Error 2
SRC_aim/compile.msg:make[1]: *** [moduls.o] Error 127
SRC_aim/compile.msg:make: *** [complex] Error 2
SRC_balsac-utils/compile.msg:make: [clean] Error 1 (ignored)
SRC_balsac-utils/compile.msg:make: *** [outnn2plt.o] Error 127
SRC_broadening/compile.msg:make: *** [broadening.o] Error 127
SRC_cif2struct/compile.msg:make: *** [module.o] Error 127
SRC_clmcopy/compile.msg:make: *** [clmcopy.o] Error 127
SRC_dstart/compile.msg:make: *** [reallocate.o] Error 127
SRC_elast/compile.msg:make: [clean] Error 1 (ignored)
SRC_elast/compile.msg:make: *** [genetempl.o] Error 127
SRC_eosfit6/compile.msg:make: [clean] Error 1 (ignored)
SRC_eosfit6/compile.msg:make: *** [eosfit6.o] Error 127
SRC_eosfit/compile.msg:make: [clean] Error 1 (ignored)
SRC_eosfit/compile.msg:make: *** [eosfit.o] Error 127
SRC_filtvec/compile.msg:make[1]: *** [filtvec.o] Error 127
SRC_filtvec/compile.msg:make: *** [real] Error 2
SRC_filtvec/compile.msg:make[1]: *** [filtvec.o] Error 127
SRC_filtvec/compile.msg:make: *** [complex] Error 2
SRC_fsgen/compile.msg:make: [clean] Error 1 (ignored)
SRC_fsgen/compile.msg:make: *** [bcc_fs_mesh.o] Error 127
SRC_initelnes/compile.msg:make: *** [initelnes.o] Error 127
SRC_initxspec/compile.msg:make: *** [initxspec.o] Error 127
SRC_irrep/compile.msg:make: *** [felder.o] Error 127
SRC_joint/compile.msg:make: *** [felder.o] Error 127
SRC_kgen/compile.msg:make: *** [main.o] Error 127
SRC_kram/compile.msg:make: *** [drude.o] Error 127
SRC_lapw0/compile.msg:make[1]: *** [modules.o] Error 127
SRC_lapw0/compile.msg:make: *** [seq] Error 2
SRC_lapw1/compile.msg:make[1]: *** [modules.o] Error 127
SRC_lapw1/compile.msg:make: *** [real] Error 2
SRC_lapw1/compile.msg:make[1]: *** [modules.o] Error 127
SRC_lapw1/compile.msg:make: *** [complex] Error 2
SRC_lapw2/compile.msg:make[1]: *** [reallocate.o] Error 127
SRC_lapw2/compile.msg:make: *** [real] Error 2
SRC_lapw2/compile.msg:make[1]: *** [reallocate.o] Error 127
SRC_lapw2/compile.msg:make: *** [complex] Error 2
SRC_lapw3/compile.msg:make[1]: *** [atomgrid.o] Error 127
SRC_lapw3/compile.msg:make: *** [real] Error 2
SRC_lapw3/compile.msg:make[1]: *** [atomgrid.o] Error 127
SRC_lapw3/compile.msg:make: *** [complex] Error 2
SRC_lapw5/compile.msg:make[1]: *** [atomgrid.o] Error 127
SRC_lapw5/compile.msg:make: *** [real] Error 2
SRC_lapw5/compile.msg:make[1]: *** [atomgrid.o] Error 127
SRC_lapw5/compile.msg:make: *** [complex] Error 2
SRC_lapw7/compile.msg:make[1]: *** [moduls.o] Error 127
SRC_lapw7/compile.msg:make: *** [real] Error 2
SRC_lapw7/compile.msg:make[1]: *** [moduls.o] Error 127
SRC_lapw7/compile.msg:make: *** [complex] Error 2
SRC_lapwdm/compile.msg:make[1]: *** [reallocate.o] Error 127
SRC_lapwdm/compile.msg:make: *** [real] Error 2
SRC_lapwdm/compile.msg:make[1]: *** [reallocate.o] Error 127
SRC_lapwdm/compile.msg:make: *** [complex] Error 2
SRC_lapwso/compile.msg:make: *** [reallocate.o] Error 127
SRC_lcore/compile.msg:make: *** [cdsld.o] Error 127
SRC_lorentz/compile.msg:make: *** [lorentz.o] Error 127
SRC_lstart/compile.msg:make: *** [cdlsd.o] Error 127
SRC_mini/compile.msg:make: *** [mxpmgrid.o] Error 127
SRC_mixer/compile.msg:make: *** [charge.o] Error 127
SRC_nn/compile.msg:make: *** [struk.o] Error 127
SRC_optic/compile.msg:make[1]: *** [modules.o] Error 127
SRC_optic/compile.msg:make: *** [real] Error 2
SRC_optic/compile.msg:make[1]: *** [modules.o] Error 127
SRC_optic/compile.msg:make: *** [complex] Error 2
SRC_optimize/compile.msg:make: [clean] Error 1 (ignored)
SRC_optimize/compile.msg:make: *** [optimize.o] Error 127
SRC_orb/compile.msg:make: *** [modules.o] Error 127
SRC_pairhess/compile.msg:make: *** [energy.o] Error 127
SRC_phonon/compile.msg:make: [clean] Error 1 (ignored)
SRC_phonon/compile.msg:make: *** [phonon2wien2k_sym.o] Error 127
SRC_qtl/compile.msg:make: *** [reallocate.o] Error 127
SRC_spacegroup/compile.msg:make: *** [spacegroup.o] Error 127
SRC_spaghetti/compile.msg:make: *** [reallocate.o] Error 127
SRC_structeditor/compile.msg:make[1]: *** [module.o] Error 127
SRC_structeditor/compile.msg:make: *** [all] Error 2
SRC_sumpara/compile.msg:make: *** [errclr.o] Error 127
SRC_supercell/compile.msg:make: *** [supercell.o] Error 127
SRC_symmetry/compile.msg:make: *** [symmetry.o] Error 127
SRC_symmetso/compile.msg:make: *** [symmetso.o] Error 127
SRC_telnes2/compile.msg:make: *** [modules.o] Error 127
SRC_tetra/compile.msg:make: *** [reallocate.o] Error 127
SRC_trig/compile.msg:make: [clean] Error 1 (ignored)
SRC_trig/compile.msg:make: *** [rhomb_in5.o] Error 127
SRC_txspec/compile.msg:make: *** [reallocate.o] Error 127
赞一下 回复此楼
…………
2楼2008-12-02 10:42:11
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

fansw1129

铁杆木虫 (著名写手)
★ ★
wuli8(金币+2,VIP+0):感谢您的交流！(*^__^*) ……能讲的更仔细些就好了。
估计是编译器没有装好
赞一下(10人) 回复此楼
3楼2008-12-02 20:42:14
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wuli8

荣誉版主 (知名作家)

…………

优秀版主优秀版主
引用回帖:
Originally posted by fansw1129 at 2008-12-2 20:42:
估计是编译器没有装好

能不能讲的具体些，谢谢
赞一下 回复此楼
…………
4楼2008-12-02 22:31:06
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖
查看全部 275 个回答
普通表情 龙 兔 虎 猫 高级回复 (可上传附件)
信息提示
关闭
请填处理意见
关闭