DELPHI盒子技术论坛 https://bbs.2ccc.com/ zh-cn Copyright 2004, bbs.2ccc.com root@2ccc.com https://bbs.2ccc.com/rss.asp Rss Generator By bbs.2ccc.com https://bbs.2ccc.com/topic.asp?topicid=769805 tms2021 回复:1 浏览:28 Sat, 03 Oct 2026 11:10:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769802 tms2021 回复:0 浏览:54 Fri, 02 Oct 2026 23:10:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769789 mp654kk 回复:3 浏览:57 Fri, 02 Oct 2026 03:10:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769770 liskman <html><body>" L"<h2>Hello,World.</h2>" L"</body></html>"; Chromium->LoadString(strHtml, L"about:blank"); 编译正常，链接时报: [ld.lld Error] ld.lld: error: undefined symbol: Ucefchromiumcore::TChromiumCore::LoadStringW(System::UnicodeString, System::UnicodeString) 使用函数 Chromium->LoadURL() 可正常编译链接, 对Delphi不熟悉，Chromium->LoadString()在C++Builder环境下的链接错误，请问是什么原因？ 请高手指点一下。]]> 回复:3 浏览:79 Thu, 01 Oct 2026 00:10:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769757 siaosa 回复:17 浏览:283 Wed, 30 Sep 2026 09:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769751 siaosa 回复:10 浏览:162 Wed, 30 Sep 2026 04:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769750 tms2021 回复:0 浏览:91 Wed, 30 Sep 2026 03:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769737 fausten 回复:11 浏览:345 Tue, 29 Sep 2026 11:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769715 emailx45 回复:3 浏览:394 Fri, 25 Sep 2026 20:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769713 emailx45 回复:0 浏览:236 Fri, 25 Sep 2026 20:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769714 emailx45 回复:1 浏览:334 Fri, 25 Sep 2026 20:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769710 emailx45 <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v NtfsDisable8dot3NameCreation /t REG_DWORD /d 3 /f</Path> <Description>Desativa a criacao de nomes no padrao 8.3 do DOS em todos os volumes NTFS</Description> </RunSynchronousCommand> </RunSynchronous> </component> </settings> </unattend> c) 现在，将此文件放在 Windows 安装光盘或 U 盘的根目录 d) 现在，像往常一样继续安装 e) 要检查新策略是否生效，您可以检查注册表中的以下键值： “HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation” 0 = 在所有卷上启用（旧版 Windows 默认设置）。 1 = 在所有卷上禁用（全新安装时需要）。 2 = 基于卷（当前设置：数据磁盘禁用，C 盘启用）。 3 = 除系统卷外，所有卷均禁用（基于卷的模式变体）。 与 MSWindows 11 兼容的操作 2（但不限于此） 2) 更改当前系统的键值： a) 即使系统已安装，您也可以更改键值，但务必权衡利弊！ b) 更改键值意味着将创建或删除“8.3 字符二级索引表”。 c) 因此，如果该表已存在，则会被删除。 d) 如果该表不存在，您可以创建它。 e) 根据该表是否存在，磁盘上的旧文件将继续正常存在，但该表是否会被创建则取决于具体情况。 f) 因此，如果系统中不再存在该二级索引表，则意味着操作系统将不再查询该表，从而不再向请求此信息的软件提供 8.3 字符二级名称。 g) 因此，更改将影响文件名索引表的结构，而不是文件数据！ h) 您可以通过更改注册表项的值（如上所示）或使用控制台命令来实现： fsutil 8dot3name strip /t /l d:\meulog.log /s c: 此示例命令不会进行任何永久性更改。它仅执行“测试”并将结果保存到日志文件中。 因此，您可以根据自身环境做出决定。 i) 如果您希望永久更改，可以使用“FSUTIL”命令的其他参数。要了解这些参数，请键入：“FSUTIL /?” 示例：“fsutil 8dot3name strip /l mylogfile.log /s D:\MyData” 删除驱动器“D”上指定目录“MyData”的短名称表。 要在驱动器“C”上使用，可以使用：“fsutil 8dot3name strip /l mylogfile.log /s C:” j) 您可以使用命令“fsutil 8dot3name query C:”来检查指令的当前状态！ k) 您可以使用命令“fsutil 8dot3name set 1”来更改系统范围内所有驱动器的指令，将值更改为“1”，如上表所示。 [b]与以往一样，影响整个操作系统的命令必须以“管理员”身份运行，否则将无法执行！[/b] ========== MS Windows 10 or 11 without the use of legacy MS-DOS 8.3 names As always, this topic resurfaces whenever system performance is a critical factor. Many know that MS-DOS was a crucial system prior to the arrival of MS Windows, as it was far easier to use than Linux—which, at the time, was largely the domain of fearless hackers. For compatibility reasons, all editions of MS Windows employed a legacy directive: accepting 8.3 character filenames, even though long filenames (up to 255 characters) were supported. This practice continued into modern versions of MS Windows and remains the default behavior during operating system installation to this day. However, MS Windows has long allowed users to disable this directive, even during the initial system setup. Doing so stops MS Windows from creating the secondary index used to store 8.3 filenames. Consequently, on systems containing hundreds of thousands or millions of files and folders, this leads to improved read and write performance. In reality, this isn't so much a performance boost as it is achieving the speed the system should have had from the start—specifically, by avoiding the overhead of creating that secondary 8.3 filename index. This change can be implemented in three ways: 1) During the initial operating system installation, by creating a file named "autounattend.xml" (if it does not already exist) with the appropriate configuration settings. 2) By modifying a specific Registry key: `HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation` 3) Via a console command to modify the Registry key: `FSUTIL` ... (parameters) Usage and side effects of modifying this legacy directive: a) USAGE: Improved file access (searching), as the system no longer needs to query the secondary index table containing 8.3 filenames. This in itself would already demonstrate a good reason for using it! b) SIDE EFFECT: only software that still requires 8.3-character filenames would be affected. This is because such software would be unable to distinguish between names like "HelloWord.txt" and "HelloW~1.txt". For modern MS Windows (10, 11, etc.), this would not be an issue, as the system reads the primary name from the long filename table. c) IMPACT ON EXISTING NAMES ON ACTIVE OR REMOVABLE DISKS: generally speaking, nothing would happen to the file data, as the files would remain intact. Only software requiring an 8.3-character filename might fail to locate the file; unable to handle long filenames, it would assume the file does not exist. d) Thus, the data would remain intact, but the filename might not be recognized by older software or software that does not support long filenames. e) On the other hand, if the file uses an 8.3-character name in the system's primary name table, this would pose no problem—even for software that does not support long filenames—since the name is already in the 8.3 format from the start. So, if you want to test the performance of your millions of files when you need to locate or use them, you could do the following: 1) OPERATING SYSTEM INSTALLATION USING THE "autounattend.xml" FILE: a) create a simple text file named "autounattend.xml" b) add the following content to the file and save it <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v NtfsDisable8dot3NameCreation /t REG_DWORD /d 3 /f</Path> <Description>Desativa a criacao de nomes no padrao 8.3 do DOS em todos os volumes NTFS</Description> </RunSynchronousCommand> </RunSynchronous> </component> </settings> </unattend> c) now, place this file at the root of your MS Windows installation disk or USB drive d) proceed with the installation as you normally would e) to check whether the new policy is in effect, you can verify the value of the following Registry key: "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation" 0 = Enabled on all volumes (Old Windows default). 1 = Disabled on all volumes (What you want for a clean installation). 2 = Volume-based (Your current configuration: disabled on data drives, enabled on C:). 3 = Disabled on all volumes except the system volume (Variation of volume-based mode). Option 2 is the default in MS Windows 11 (and possibly in others as well). 2) CHANGING THE KEY VALUE FOR THE CURRENTLY RUNNING SYSTEM: a) you can change the key value even after the system is installed, always taking care to weigh the pros and cons! b) changing the key value means that the "8.3 character secondary index table" will be created or deleted. c) thus, if it exists, it will be deleted. d) if it does not exist, you can create it. e) regardless of whether it exists or not, existing files on the disk will remain intact, but the table will either be created or removed. f) Thus, if the secondary table ceases to exist in the system, the operating system will no longer consult this table to provide the 8.3-character secondary name to software requesting this information. g) Therefore, the change is structural—affecting the file name index table rather than the actual file data! h) You can do this by changing the Registry key value, as shown above, or via a console command: fsutil 8dot3name strip /t /l d:\meulog.log /s c: This example command does not make any permanent changes; it merely performs a "test" and saves the results to a log file. This allows you to make a decision based on your specific environment. i) If you wish to implement the changes, you can use other "FSUTIL" command parameters; to view the available parameters, type: "FSUTIL /?" Example: "fsutil 8dot3name strip /l mylogfile.log /s D:\MyData" This removes the short name table for the specified directory "MyData" on drive "D". To use it on drive "C", you could use: "fsutil 8dot3name strip /l mylogfile.log /s C:" j) You can use the command "fsutil 8dot3name query C:" to check the current status of the policy! k) You can use the command "fsutil 8dot3name set 1" to change the policy across the entire system and all drives, setting the value to "1" as shown in the table above. [b]As always, commands that affect the operating system in general must be run as "administrator"; otherwise, they will not execute.[/b]]]> 回复:1 浏览:102 Fri, 25 Sep 2026 19:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769701 cnpack 回复:15 浏览:335 Fri, 25 Sep 2026 11:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769699 cxg417 回复:1 浏览:130 Fri, 25 Sep 2026 02:09:00 GMT https://bbs.2ccc.com/topic.asp?topicid=769695 emailx45 回复:2 浏览:324 Thu, 24 Sep 2026 21:09:00 GMT