世博就是数字电视大渣会,一个比一个大。
世博就是走”S”弯,一个接着一个走。
世博就是匆匆走,走完一程继续走。
世博就是人看人,你看他来我看你。
世博就是比体力,看你还能站多久。
世博就是捉迷藏,不知馆里能看啥。
Posted with wordpress for blackberry.
世博就是数字电视大渣会,一个比一个大。
世博就是走”S”弯,一个接着一个走。
世博就是匆匆走,走完一程继续走。
世博就是人看人,你看他来我看你。
世博就是比体力,看你还能站多久。
世博就是捉迷藏,不知馆里能看啥。
Posted with wordpress for blackberry.
警告: 本文仅供学习与参考之用.请使用合法正版的软件.梦想天空对文章内容不承担任何责任.
Warning: This article is for your study and reference only. Please use legitimate genuine software. DreamingSky will NOT be responsible for its content.
使用带有SLIC 2.1的BIOS在Vmware Workstation 7中激活OEM Windows 7
1. 提取原版BIOS
在Vmware Workstation 7的安装文件夹中找到vmware-vmx.exe文件(如果宿主系统是x64系统则该文件位于安装文件夹的x64\子文件夹中),复制到临时文件夹,通过右键菜单使用7-zip释放出其中的各个区段,在.rsrc\BINRES\文件夹中的6006即是Vmware Workstation 7的BIOS.方便起见可以将6006复制一份副本并重命名为vmwbios.rom.
2. 修改BIOS
使用Phoenix BIOS Editor Pro 2.2.0.1打开vmwbios.rom并且在以下过程中该文件必须保持打开状态!
2.1 使用010 Editor打开相应品牌的SLIC 2.1文件,如LENOVO.BIN,查看文件开始第9字节起的14个字节并将其复制,如联想某个SLIC 2.1为"LENOVOTC-5M "(最后3位为空格,不带双引号).
2.2 浏览Phoenix BIOS Editor Pro所在文件夹中的TEMP子文件夹,使用010 Editor打开BIOSCOD0.ROM,搜索rsdt,类型为ASCII字符串,会找到三处.在第一处找到的rsdt前后均有"INTEL 440BX "(最后3位为空格,共14个字符)字符串,替换为刚才复制的14位OEM标识字符串,保存.
2.3 将相应品牌的SLIC文件复制到Phoenix BIOS Editor Pro的TEMP子文件夹中.
2.4 使用010 Editor打开TEMP子文件夹中的ROM.SCR文件. 在文件末尾添加SLIC文件信息,如"ACPI LENOVO.BIN".
2.5 回到Phoenix BIOS Editor Pro窗口,点击DMI Strings窗口,双击Motherboard Version右侧的’None’,在弹出对话框中输入相应的OEM标识字符串,例如联想则输入’LEGEND Dragon’(包括单引号),确定.
2.6 从File菜单选择Build BIOS…构建新的BIOS.
至此BIOS已经修改完毕.
3. 修改虚拟机配置
在Vmware Workstation 7中全新安装Windows 7或使用现有虚拟机,复制vmwbios.rom到虚拟机所在文件夹,打开该文件夹找到*.vmx虚拟机配置文件,使用010 Editor打开并在末尾加入[bios440.filename = "vmwbios.rom"](不包含[]).
4. 完成激活
在Vmware Workstation 7中启动Windows 7,将OEM证书文件(*.xrm-ms)复制入虚拟系统根文件夹.以管理员身份运行命令提示符(cmd.exe),安装证书,如"slmgr.vbs -ilc c:\lenovo.xrm-ms". 等待成功确认对话框出现后继续输入密钥激活,如"slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"(xxxxx代表相应的密钥).等待成功确认对话框出现即告激活正式完成.
Unsolved problem:
When generate the shell profile ,,this error encountered.
Error 20507 signalled when creating profile JAT23:
The space curve consists of more than one curve branch.!
Now ,the profile is generated like this. It’s used Bulb bar (230,13),
This log message show the error about there are no intersections in the edges of the shell plate when create the shell plate.
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
No intersection between the edges 1 and 2
_DP2 STRIP= X NUMBER OF STRIPS= 8
_DP2 GAP= 0.00 AT EDGE 1
_DP2 GAP= 0.02 AT EDGE 2
_DP2 GAP= 0.00 AT EDGE 3
_DP2 GAP= 0.02 AT EDGE 4
_DP2 GAP= 0.02 AT THE BASELINE
No intersection between the edges 1 and 3
No intersection between the edges 1 and 2
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
WG936D – entry 0
WG939D – entry 0
WG939D – exit 0
WG936D – exit 0
Error 11005 occurred when defining edge 3
the solution : extend your seam or butt about 50mm , it could ensure the intersections is existent when system calculate the edges of shell plates.
This is a sample about the Shell Seam and Butt define. The highlight part show that it’s a shell plate , The sketch nearby is the shell plate developed sketch.In tribon the designer could check the developed sketch realtime. It help that the designer could adjust the seam and butt arrangement to save the material and manhour.
this is the pic about it.
This message shows the Server is started normally.
========================================================================================================================
tribon Surface Server version 3, 0, 5, 24
Started Sat Aug 21 14:24:04 2010
Logging information will be printed below
This message shows the error when the server can’t find the DML file
—————————————————————————————————-
tribon Surface Server version 3, 0, 5, 24, started Sat Aug 21 14:24:04 2010
Current time is Sat Aug 21 14:24:52 2010
Surface : MYHULL
Folder : C:\Tribon\M3\Projects\MY\TID\
Box : -1000000.000 0.000 -1000000.000 1000000.000 1000000.000 1000000.000
Surface folder: C:\Tribon\M3\Projects\MY\TID\
Surface name: MYHULL
Ambiguous name MYHULL. Access (dml/dms/dm/sat) = -1/-1/-1/-1
Loading MYHULL
Opening model MYHULL
ERROR: cannot open MYHULL
This message shows the server servie the client successfully.
—————————————————————————————————-
Tribon Surface Server version 3, 0, 5, 24, started Sat Aug 21 14:39:51 2010
Current time is Sat Aug 21 14:40:25 2010
Surface : MYHULL
Folder : C:\Tribon\M3\Projects\MY\TID\
Box : -1000000.000 0.000 -1000000.000 1000000.000 1000000.000 1000000.000
Surface mapped to MYHULL.dml
Surface folder: C:\Tribon\M3\Projects\MY\TID\
Surface name: MYHULL.dml
Loading MYHULL.dml
Opening model MYHULL.dml
File type is DML, source 0
PLANAR INTERSECTION Intersecting MYHULL.dml with plane 1.0000 0.0000 0.0000 18950.0000 Opening DML: MYHULL.dml Raw data: 200 points across 11 curved patches. 2 points across 1 plane patches Intersected with tol= 0.000500, Thinned with tol= 0.000500 Number of contours = 1 Contour 1 . X Y Z dX dY dZ . 1 18950.000 0.000 0.000 0.000000 1.000000 0.000000 . 2 18950.000 586.064 0.000 0.000000 1.000000 0.000000 . 3 18950.000 827.355 11.998 0.000000 0.995559 0.094144 . 4 18950.000 1411.268 110.644 0.000000 0.975053 0.221970 . 5 18950.000 1620.101 161.826 0.000000 0.967241 0.253859 . 6 18950.000 2362.602 383.143 0.000000 0.958322 0.285690 . 7 18950.000 2767.010 489.338 0.000000 0.978324 0.207080 . 8 18950.000 3000.000 527.557 0.000000 0.994333 0.106314 . 9 18950.000 3000.000 527.557 0.000000 0.975510 0.219954 . 10 18950.000 3224.779 576.931 0.000000 0.976828 0.214026 . 11 18950.000 3403.990 620.286 0.000000 0.962962 0.269636 . 12 18950.000 3657.842 720.555 0.000000 0.876068 0.482188 . 13 18950.000 3996.469 1014.821 0.000000 0.632749 0.774357 . 14 18950.000 4221.738 1346.601 0.000000 0.503711 0.863872 . 15 18950.000 4457.530 1800.000 0.000000 0.431649 0.902042 . 16 18950.000 4457.530 1800.000 0.000000 0.509716 0.860343 . 17 18950.000 4560.312 1950.543 0.000000 0.590499 0.807038 . 18 18950.000 4632.418 2049.459 0.000000 0.582080 0.813131 . 19 18950.000 4840.605 2360.202 0.000000 0.546179 0.837668 . 20 18950.000 5046.285 2700.000 0.000000 0.471634 0.881794 . 21 18950.000 5046.285 2700.000 0.000000 0.448536 0.893765 . 22 18950.000 5215.380 3043.745 0.000000 0.450761 0.892645 . 23 18950.000 5480.669 3508.026 0.000000 0.540749 0.841184 . 24 18950.000 5721.855 3830.647 0.000000 0.664354 0.747418 . 25 18950.000 5785.979 3900.000 0.000000 0.694992 0.719018 . 26 18950.000 6000.000 4109.988 0.000000 0.727537 0.686068 . 27 18950.000 6354.406 4414.577 0.000000 0.791015 0.611797 . 28 18950.000 6888.679 4768.924 0.000000 0.866357 0.499425 . 29 18950.000 7380.019 5033.305 0.000000 0.891693 0.452641 . 30 18950.000 8063.873 5356.022 0.000000 0.917262 0.398284 . 31 18950.000 8451.559 5522.410 0.000000 0.915386 0.402578 . 32 18950.000 9000.000 5812.491 0.000000 0.825994 0.563679 . 33 18950.000 9000.000 5812.491 0.000000 0.855004 0.518621 . 34 18950.000 9293.611 5993.888 0.000000 0.846026 0.533142 . 35 18950.000 10126.320 6559.392 0.000000 0.803914 0.594745 . 36 18950.000 10804.766 7105.598 0.000000 0.752444 0.658657 . 37 18950.000 11324.114 7591.044 0.000000 0.708432 0.705780 . 38 18950.000 12000.000 8332.877 0.000000 0.633030 0.774127 . 39 18950.000 12605.158 9161.275 0.000000 0.551897 0.833912 . 40 18950.000 12930.607 9679.715 0.000000 0.511085 0.859530 . 41 18950.000 13406.640 10565.402 0.000000 0.432846 0.901468 . 42 18950.000 13783.842 11454.700 0.000000 0.346974 0.937875 . 43 18950.000 13992.473 12064.226 0.000000 0.305153 0.952303 . 44 18950.000 14330.000 13156.619 0.000000 0.300845 0.953673 . 45 18950.000 14510.628 13752.479 0.000000 0.282516 0.959263 . 46 18950.000 14762.328 14646.378 0.000000 0.254767 0.967002 . 47 18950.000 15000.000 15648.329 0.000000 0.208095 0.978109 . 48 18950.000 15023.984 15762.089 0.000000 0.204509 0.978865 . 49 18950.000 15244.386 16888.232 0.000000 0.181897 0.983318 . 50 18950.000 15401.588 17784.530 0.000000 0.162708 0.986674 . 51 18950.000 15559.663 18829.341 0.000000 0.135080 0.990835 . 52 18950.000 15609.118 19208.108 0.000000 0.123874 0.992298 Processing time was 0.05/0.05 seconds Process size 29.3/29.3 Mb Totals: Lines Ints(1), Surface Ints(0), Foreign Ints(0), Gen Cyls(0), Ext Curves(0) ----------------------------------------------------------------------------------------------------
By the way ,the TID server log file is in ($windows)\temp\ floder.
收藏:http://www.cnblogs.com/zhou__zhou/archive/2010/05/22/1741386.html
Step 1:Creating a Linked Server.
EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5', 'ADSDSOObject', 'adsdatasource'
Step 2:Creating a SQL Server Authenticated Login
EXEC sp_addlinkedsrvlogin @rmtsrvname = N'ADSI', @locallogin = NULL , @useself = N'False', @rmtuser = N'domain\Account', @rmtpassword = N'Password'
对于 SQL Server 授权登录,可以使用sp_addlinkedsrvlogin 系统存储过程配置用于连接到目录服务的适当的登录/密码.
如果SQLServer使用Windows 授权登录,只需自映射就足以通过使用 SQL Server 安全委托来访问AD。简单点说就是直接运行第三步语句即可.
Step 3:Querying the Directory Service.
-- Query for a list of User entries in an OU using the SQL query dialect select convert(varchar(50), [Name]) as FullName, convert(varchar(50), Title) as Title, convert(varchar(50), TelephoneNumber) as PhoneNumber from openquery(ADSI, 'select Name, Title, TelephoneNumber from ''LDAP://OU=Directors,OU=Atlanta,OU=Intellinet,DC=vizability,DC=intellinet,DC=com' ' where objectClass = ''User''') -- Query for a list of Group entries in an OU using the SQL query dialect select convert(varchar(50), [Name]) as GroupName, convert(varchar(50), [Description]) GroupDescription from openquery(ADSI, 'select Name, Description from ''LDAP://OU=VizAbility Groups,DC=vizability,DC=intellinet,DC=com'' where objectClass = ''Group''')
引用:
http://msdn2.microsoft.com/en-us/library/aa772380.aspx
http://www.atlantamdf.com/presentations/AtlantaMDF_111201_examples.txt
说明:但是这样默认查询出来的是1000个对象.怎么办呢?
方法一,通过字母来循环.见以下:
CREATE TABLE #tmpADUsers ( employeeId varchar(10) NULL, SAMAccountName varchar(255) NOT NULL, email varchar(255) NULL) GO /**//* AD is limited to send 1000 records in one batch. In an ADO interface you can define this batch size, not in OPENQUERY. Because of this limitation, we just loop through the alphabet. */ DECLARE @cmdstr varchar(255) DECLARE @nAsciiValue smallint DECLARE @sChar char(1) SELECT @nAsciiValue = 65 WHILE @nAsciiValue < 91 BEGIN SELECT @sChar= CHAR(@nAsciiValue) EXEC master..xp_sprintf @cmdstr OUTPUT, 'SELECT employeeId, SAMAccountName, Mail FROM OPENQUERY( ADSI, ''SELECT Mail, SAMAccountName, employeeID FROM ''''LDAP://dc=central,dc=mydomain,dc=int''''WHERE objectCategory = ''''Person'''' AND SAMAccountName = ''''%s*'''''' )', @sChar INSERT #tmpADUsers EXEC( @cmdstr ) SELECT @nAsciiValue = @nAsciiValue + 1 END DROP TABLE #tmpADUsers
以上方法源自于:http://www.sqlservercentral.com/Forums/Topic231658-54-1.aspx#bm231954
我推荐的方法:在微软搜索到的.如何通过 NTDSUtil为服务器修改限制 maxPageSize
1.Click Start, and then click Run.
2.In the Open text box, type ntdsutil, and then press ENTER. To view help at any time, type ? at the command prompt.
Modifying policy settings
1.At the Ntdsutil.exe command prompt, type LDAP policies, and then press ENTER.
2.At the LDAP policy command prompt, type Set setting to variable, and then press ENTER. For example, type Set MaxPoolThreads to 8.
This setting changes if you add another processor to your server.
3.You can use the Show Values command to verify your changes.
To save the changes, use Commit Changes.
4.When you finish, type q, and then press ENTER.
5.To quit Ntdsutil.exe, at the command prompt, type q, and then press ENTER.
资料来源:
http://support.microsoft.com/kb/315071/en-us
http://support.microsoft.com/?scid=kb%3Bzh-cn%3B299410&x=16&y=10
如何使用SQL查询活动目录对象语法: http://www.microsoft.com/china/technet/community/columns/scripts/sg0505.mspx#EMBAC
The first of work of using Curved hull is generating hull curves for checking the surface .Because maybe there are some errors in the surface created by other software such as tribon. If those curves could be generated, it show the surface is suitable for Curved hull model. Those pictures is of a bulk ship.
Next, I will define the beam and butt .
刘二双
(广船国际技术中心)
摘 要:本文主要介绍了tribon M2系统的系统文件D065文件的组成。结构、作用过程、及其在舾装设计中的应用。
关键词:项目 子项目 系统文件 关键字 数据库 指针
在tribon M2系统中.有一个极为重要的系统文件,这个系统文件的文件名格式为d065<project>.sbd。其中<project>为船舶产品的工程代号,一般为两位字母(最多可以达到八个字母或数字)。每一个船舶产品的项目对应着一个d065<project>.sbd文件。TRIBON系统对所有船舶产品模型的数据以及系统本身所用到的系统变量文件的访问都是通过这个文件来控制的,可以说,d065<project>.sbd文件是TRIBON M2系统的灵魂,没有这个系统文件,TRIBON M2系统的程序就无法正常运行
1 dO65<project>.sbd:~件的组成结构dO65<project>.sbd文件是一个文本文件,由关键字(也就是系统变量)及其参数值组成。每个关键字及其参数值单独占一行,关键字和它的参数值之间用空格隔开。不同的关键字在文件中出现的先后次序对其作用没有什么影响.但是如果同一个关键字在文件中出现了两次.则系统以最后出现的关键字值为准。
d065<project>.sbd文件中的关键字可分成几类:
数据库文件指针
环境变量文件指针
数据服务器及数据库文件路径指针
其它文件路径指针
系统变量
standalone project must be tansfer to PIM for the next wroks.
five key points:
1 SB_TID should be set up and point to a databank.
2 SB_NAVARCH should be set up and point to a standalone project folder.
3 Export the TID project by using the Initial Design Project Tool
4 Import the TID export file into the PIM.
5 Using Initiate Hull Standards, register the names of any released Hull Forms, Envelopes or Surfaces which are to be used as sculptured surfaces in Basic Design or Hull.
I have transfered it successfully.
前段时间开始利用业余时间学习tribon,给自己定的一个目标就是从0开始把整个工程从线型开始到最后的梄装结束整个流程做完。每天必须首先保证日常工作完成后才能顺用一些空余和休息时间来学习。在接下来的时间里,我会将的我学习中遇到的相关问题记录下来,同时也与大家分亨一下经验。
我总共花了五星期业余时间把46000T油船的线型光顺完成,直至生成曲面。当然其中也还存在一些问题。我只是把整个流程走完,如果有更多的资料和时间应该能做得更细致一些。今天有点时间把线型这块的内容学习过程写出来和大家分亨。
学习准备工作的第一步就是准备资料。tribon面向船舶专业,不是通用型的设计软件,因此相关资料很少,即使有,也只是简单的翻译一下原文,这样的手册还不如看英文原版。我主要是参考了tribon M3 line Training Guide.这本资料是官方的资料。官方资料主要是对软件的功能进行了描述,而我们最需要的是能将如何将型线图及型值表中的数据直至生成曲面的整个过程 的资料。可惜找不到这样的资料。只能从这本资料下手了。
1、型值数据输入
通常我们都会有CAD版的型线图,我们需要一个工具来采样条曲线上的每个点。这些点在LINE中用来拟合曲线(水线,侧剖线,纵剖线等)。沈哥给予了我很大帮助,他给了我一个采集程序,这个程序在CAD中采集可以直接输出到EXCEL中,然后由EXCEL处理后导出为TXT,再RENAME为DAT文件,最后导进LINE中。一条水线上有上百个点,而且水线在投影面上很密集,采集点很容易出错。每次采集我都把这条线变个颜色后再采集,可以减少错误。采集后在EXCEL中进入处理,主要是增加坐标,因为采集的是平面点,而输入LINE中是大部分是需要三维点。46000T大约80条线,花费了十多小时采集处理。
另:到后来我发现用CAD的LIST命令比那个程序采集要快,LIST后复制出来替换,就行了。等我有时间了我会用ARX编一个自动采集处理的程序来解决这个问题。 继续阅读
source:http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7
Many of you, like myself, have started running Windows 7 as their primary desktop OS and find it to be a massive improvement over Windows Vista on so many levels.
One of the very few inconveniences I have found with it, and this is not an bug or problem with Windows 7 itself, is the inability to run the VMware vSphere Client.
UPDATE: Good News – This issue has now been resolved in VMware ESX/ESXi 4.0 Update 1 (U1).
When attempting to run the client the following errors are received and you are unable to proceed any further:
“Error parsing the server “<server name” “clients.xml” file.”

“The type initializer for ‘VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.”
