VCD????????????????

VCD tår for Video Compact Disc - og er en film.

Se den med PowerDVD

VCD = video cd

doh

VCD filer hedder *.dat, så det er ikke en Video CD fil du har fået fat i.

Der er et program der bruger den, men om du selv skal bruge den er jeg lidt i tvivl om.

Her er hvad jeg fandt:

.VCD      Virtual Communications Driver

http://www.springfieldtech.com/HOW_DO/File_type.htm

du kan bruge mediaplayer...det ligger som standard på de fleste pc\'er

Hvad hedder det program, der kan køre VCD

CyberLinks PowerDVD, som jeg har skrevet en gang

må man spørge hvorfor du afviser svarene?

Du skal nok ikke regne med at der er et program der kan køre *.vcd filen, hvis du ser hvad \"james t dk\" har skrevet så står der \"Virtual Communications Driver\" dvs. det er en slags driver.

Her er svaret:

http://support.microsoft.com/support/kb/articles/Q76/5/64.ASP

Receiving a Physical COM Port from the Windows VCD

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows Device Development Kit (DDK) for Windows, versions 3.0, 3.1

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


SUMMARY
In the enhanced mode of the Microsoft Windows graphical environment, the virtual communications device (VCD) assigns a physical communications (COM) port to a virtual machine (VM) only when certain events occur. The text below lists these events.



MORE INFORMATION
In Windows enhanced mode, the VCD virtualizes and serializes the ownership of physical COM ports. When a program running in a VM directly accesses one of the I/O ports of a COM port (for example, COM1 corresponds to I/O ports 0x3F8 through 0x3FE), that VM may not necessarily own the physical port. The VM communicates with a virtual COM port until the VCD assigns a physical port.

Seven conditions that cause the VCD to assign a physical COM port to a particular VM are:



When an application reads or writes the Receive/Transmit buffer with the Divisor Latch Access Bit (80h) of the Line Control Register off.


When an application reads the Line Status Register more than once.


When an application reads the Modem Status Register more than once.


When an application writes to the Modem Control Register with the Loopback (10h) or Interrupt Enable (08h) bits on (simply changing the DTR or RTS line states does not cause VCD to assign a physical COM port).


When an application unmasks a COM port interrupt.


When a COM port interrupt occurs for an unowned COM port.


When the communications driver (COMM.DRV) instructs the VCD to assign a port to the Windows (system) VM because an application called the OpenComm function.


Implementation details on COM port assignment can be found by examining the source code to VCD, which is available in the DDK. Some of the relevant procedures are:
======================================================================
VCD_Attach called by:  VCD_Set_Owner

VCD_Detach called by:
  VCD_Set_Owner

VCD_Set_Owner called by:
  VCD_Assign
  VCD_Set_Port_Global
  VCD_PM_Acquire_Port
  VCD_PM_Free_Port
  VCD_Set_Focus
  VCD_Set_Owner_Event
  VCD_Detach_If_Owner

VCD_Assign called by:
  VCD_PM_Steal_Port
  VCD_Cant_Virtualize
  VCD_Mask

VCD_PM_Steal_Port called by:
  Comm Driver KickTx/StealPort

VCD_Cant_Virtualize called by:
  VCD_Virt_In_Out_RxTxB  (Condition 1)
  VCD_Virt_In_LSR      (Condition 2)
  VCD_Virt_In_MSR      (Condition 3)
  VCD_Virt_Out_MCR  (Condition 4)

VCD_Mask called by:
  VCD_handler (VPICD Mask_Change_Proc)  (Condition 5)

VCD_PM_Acquire_Port called by:
  Comm Driver GetCOMport386    (Condition 7)

VCD_PM_Free_Port called by:
  Comm Driver ReleaseCOMport386

VCD_Set_Owner_Event called by:
  VCD_Int        (Condition 6)

VCD_Detach_If_Owner called by:
  VCD_Destroy_VM

Additional query words: 3.00 3.10 DDKCOMM

Og hvis det er rigtigt, så bør du ikke rode med at åbne *.vcd filer, du risikere at vælte dit system.

http://support.microsoft.com/support/kb/articles/Q174/0/18.ASP?LN=EN-US&SD=gn&FR=0&qry=vcd%20file&rnk=5&src=DHCS_MSPSS_gn_SRCH&SPR=W95


Real-mode VxDs can be loaded into memory in any of the following ways:


Real-mode device drivers or TSRs that respond to the Windows 95 INT2F broadcast load their embedded VxDs when Windows 95 starts.


Drivers internal to the Vmm32.vxd file that are not \"marked\" are loaded from the following registry key:
        HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\VxD
If the real-mode virtual device driver loader finds a \"marked\" driver, it changes its registry entry from a VxD (a driver preceded with an asterix \"*\") to a file with a .vxd extension so that the external driver is found in the Windows\\System\\Vmm32 folder. When the external driver is found, it is loaded into memory.


VxDs that are not already loaded by the Vmm32.vxd file are loaded from the [386 Enh] section of the Windows\\System.ini file.


Some VxDs are required for Windows 95 to run properly. These required VxDs are loaded automatically and do not require a registry entry. The following VxDs are required by Windows 95:
      *BIOSXLAT  *CONFIGMG    *DYNAPAGE
      *DOSMGR    *EBIOS      *IFSMGR
      *INT13      *IOS        *PAGESWAP
      *SHELL      *V86MMGR    *VCD
      *VCACHE    *VCOMM      *VCOND
      *VDD        *VDMAD      *VFAT
      *VKD        *VMCPD      *VPICD
      *VTD        *VTDAPI      *VWIN32
      *VXDLDR






The real-mode virtual device driver loader checks that all required VxDs loaded sucessfully. If not, it attempts to load the drivers again.


Once the real-mode virtual device driver loading is logged, driver initialization occurs. If there are any VxDs that require real-mode initialization, they begin their process in real-mode.


Vmm32 switches the computer\'s processor from real-mode to protected- mode.


A three-phase VxD initialization process occurs in which the drivers are loaded according to their InitDevice instead of the order in which they are loaded into memory. The VxDs are carried out in the following sequence:


SYS_CRITICAL_INIT (SYSCRITINIT):

Interrupts are disabled during this phase. This gives VxDs time to prepare for device initialization without being interrupted by the system. No file I/O is allowed during SYSCRITINIT, so all SYSCRITINITs are not written to the Bootlog.txt file until after SYSCRITINIT is complete for all VxDs.


SYS_DEVICE_INIT (DEVICEINIT)

The bulk of the VxD initialization takes place during this phase. File I/O is allowed during DEVICEINIT, so each VxD\'s DEVICEINIT is logged as it occurs. The one exception is during Ifsmgr\'s DEVICEINIT. Ifsmgr takes over the real-mode file system, and disk I/O is not allowed until Ifsmgr\'s DEVICEINIT succeeds. For this reason, Ifsmgr does not appear in the DEVICEINIT phase.

When a DevLoader VxD is called, it loads other drivers it is responsible for, regardless of their InitDevice order. The DevLoader examines the Registry and finds drivers (for example, portdrivers [such as.mpd files]) and any associated support drivers. It then initializes the device associated with these drivers. During this phase, if a VxD failed to initialize, it was unable to properly communicate with the hardware or service it drives. Typically, this is due to incorrect hardware settings or the service not being installed.

The remaining static VxDs continue with the initialization phase. Also, dynamic VxDs may begin initializing during this phase. They do not have a SYSCRITINIT phase. However, a dynamic VxD may also load anytime after Windows 95 has started.


SYS_INIT_COMPLETE (INITCOMPLETE)

VxDs that successfully pass the InitComplete phase should be working properly. If a VxD was listed in one of the previous phases but is not successful in this phase, that VxD is unloaded from memory.

GUI Components:

After all the static VxDs are loaded, the Krnl32.dll, Gdi.exe, User.exe, and Explorer.exe (the default Windows 95 shell) files are loaded.

Fuck, Jer jeg fandt et program er kunne åbne VCD filer og det hedder Vitual Drive 6.0, så zero points til jer spader........

Fedt points til mig selv...