Sender: wwwwww (sleepy), the letter area: Programming Title: Regarding VXD issued station: BBS Shuimu Tsinghua Station (Mon Feb 16 02:46:39 1998) VXD is global relative to all applications That is to say that the application can access global variables in VXD directly. This is confirmed. The current question is: 1. Are all VXDs in the same linear address space? How much is the length of this linear address space? If it is 4GB, how can that other applications can see these VXDs? If you can't see it, it is impossible to implement the data shares mentioned earlier. 2. VXD also has data segments, code segments? Because there are these concepts when writing VXD, which can conducive to the read-only characteristics of the code segment. I want to ask: these data segments, and code segments are also in the same linear address space? - ※ Source: · BBS Shuimu Tsinghua Station BBS.Net.Tsinghua.edu.cn · [From: 166.111.8.130] Sender: Cohen (Tommy), Word Area: Programming Title: Re: About VXD issuance Station: BBS Shuimu Tsinghua Station (Mon Feb 16 15:19:08 1998) [In the Wwwww "masterpiece mentioned:]: VXD is global,: also said app You can directly access: global variables. This is confirmed. : The question now is: 1. Are all VXDs in the same linear address space? NBSP; ^^^^^^^^^^^^ ^^^^^^^^ It is like this, from Microsoft's information to see VXD occupied 2G The above system space, while the application space is below 2g? NBSP;: How much is the length of this linear address space? : If it is 4GB, how can that other applications can see these vxd? : If you can't see it, it is impossible to implement the data sharing mentioned earlier. : 2. VXD also has data segments, code segments? Because there are these concepts when writing VXD, this can benefit the read-only characteristics of the code segment. I want to ask: these data segments,: and code segments are also in the same linear address space? - ※ Source: · BBS Shuimu Tsinghua Station bbs.net.tsinghua.edu.cn · [From: 166.111.74.242] Sender: SUXM (Stupid), Channel: Programming Title: Re: Regarding VXD信 站: BBS Shuimu Tsinghua Station (Mon Feb 16 16:40:32 1998) [In the Wwwwww (sleepy) masterpiece:]: VXD is globally based on all applications,: also The program can access the global variable directly to the VXD. This is confirmed. ~~~~~~~~ It is true that the question is: 1.
Are all VXDs in the same linear address space? ~~~~~~~~~~~~~~~~~ Yes: What is the length of this linear address space? ~~~~~~~~~~~~~ 2GB: If it is 4GB, how can you see these VXDs? : If you can't see it, it is impossible to implement the data sharing mentioned earlier. The first 2GB space of each application has a copy of the system VXD. These copies are mapped to the same memory RAM address. This way, the application can only take advantage of the address space between 2GB ---- 4GB. : 2. VXD also has data segments, code segments? Because there is these concepts when writing VXD, ~~~~~~~~~~~~~~~~ cs = DS = SS, in the concept of forget, the concept of the forgotten segment, although the CPU is still in the prevention Say: This can benefit the read-only characteristics of the code segment. I want to ask: these data segments,: and code segments are also in the same linear address space? ~~~~~~~~~~~~~~~~~ Because CS = DS = SS, it is set in the same address space - ___________________ eat sleep eat, sleep, sleep, sleep, sleep ___________________ ※ Modification: · SUXM Feb 16 18:46:06 This article · [From: 166.111.8.153] ※ Modification: · SUXM in Feb 16 18:52:16 Modified here · [From: 166.111.8.153] ※ Source: · BBS Shuimu Tsinghua Station BBS. Net.Tsinghua.edu.cn · [from: 166.111.146.241] Sender: wwwwww (sleepy), the letter area: Programming Title: Re: About VXD issued station: BBS Shuimu Tsinghua Station (Mon Feb 16 18 : 58: 51 1998) Thank you for your guidance. The younger brother is not unknown: If the 32-bit application is in the same 4GB space in the same 4GB, that application can naturally use the pointer to access global variables in VXD. I don't understand: Is that VXD uses a pointer to access global variables in the application? If you can, don't you mess? ----- If you run the copy of the application at the same time, which application is accessed in the application? [In the masterpiece of SUXM (stupid):]: ~~~~~~~~: It is true: ~~~~~~~~~~~~~~~~~: Yes: ~ ~~~~~~~~~~~~:2GB: The first 2GB space of each application has a copy of the system VXD. : These copies are mapped to the same memory RAM address. : This way the application can only take up the address space between 2GB ----- 4GB.
: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0000-00-00 ~~~~~~~~~~~~~: Because CS = DS = SS is scheduled to be in the same address space - ※ Source: · BBS Shuimu Tsinghua Station bbs.net.tsinghua.edu.cn · [from: 166.111.8.153] Sender: wwj (Red Dust smiling), the letter area: Programming Title: Re: About VXD issued station: BBS Shuimu Tsinghua Station (Tue Feb 17 08:49:02 1998) [in wwwww In the masterpiece, it is mentioned in the masterpiece:] Win95 Win32 part is not based on paragraph management, and all of its virtual gums and its protection features are basically used by page management.: If 32-bit applications are in vxd In the same 4GB space, the application can naturally use the pointer to access global variables in VXD directly.
The virtual address where VXD is located is the same in each VM. But from the perspective of the operating system, this area should not allow the application to read and write .Win95 design for efficiency and certain aspects. These zones can be read from the application level, even some places can be written by the application.: Do not understand: That VXD can use the pointer to access the application: global variable? If you can, don't you mess? ----- If: At the same time, run the copy of the application, which application of VXD is accessed: What is the global variable? From the perspective of VXD, low 2G space is the application. That is, when the CPU runs to a certain piece of code of VXD, the low 2G space seen by VXD is this VM impression, and cannot be specified Which application; which application is, VXD should perform Processid judgment. In principle, the operating system is data that can read and write applications. - ※ Source: · BBS Shuimu Tsinghua Station BBS.NET.TSINGHUA.EDU. CN · [from: 166.11.1.8.123] Sender: Holly (HOLLY), letter area: Programming Title: Re: About VXD issued station: BBS Shuimu Tsinghua Station (Tue Feb 17 11:20:06 1998) In the masterpiece of WWJ (red dust):]: Win95 Win32 part is not based on paragraph management, all of its virtual gums and its protection characteristics: Basically, all page management is used.: VXD The virtual address is the same in each VM. However, from the perspective of the operating system, this area should: should not allow the application to read and write. Win95 design for efficiency and certain considerations, these District: Domain can be read from the application level, even some places can also be written by the application. ... No. Vxd Running On Ring 0 and apps running on ring 3: From VXD angle view, low 2G space It is the application related. That is, when the CPU runs: When the VXD is a certain piece of code, the low 2G space seen by VXD is this VM impression, and cannot be specified: an application; which application is VxD should be judged by Processid. In principle, the operating system: It is data that can read and write applications. - ※ Source: · BBS Shuimu Tsinghua Station bbs.Net.tsinghua.edu.cn · [From: 202.120.26.243 ] Sender: SUXM (stupid), letter area: Programming Title: Re: About VXD issues: BBS Shuimu Tsinghua Station (Tue Feb 17 12:50:38 1998) Memory Allocated in a vxd is Globally, And Can Be Shared with Applications.Memory That An Application Allocates May Be in a Process Specific Reg Ion of the memory map. : The younger brother still does not know:: If the 32-bit application is in the same 4GB space in the 32-bit application, the application can naturally use the pointer to access global variables in VXD directly.
