attention :: 怎样打开或关闭 CD-ROM

最新推荐文章于 2025-12-05 20:06:19 发布

原创最新推荐文章于 2025-12-05 20:06:19 发布 · 1.2k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#string #dll #function #windows #vb

博客介绍了在VB中通过向Windows Multimedia DLL发送命令来打开或关闭CD-ROM的方法。需先在模块文件中声明DLL，随后给出了打开和关闭CD-ROM的具体代码示例。

如果你想通过VB打开或者关闭CD-ROM，你可以向Windows Multimedia DLL发出一条相关的命令请求，但是你必须先声明DLL：

在模块文件中加入以下代码：

Declare Function mciSendString Lib "winmm.dll" Alias _"mciSendStringA" (ByVal lpstrCommand As String, ByVal _lpstrReturnString As String, ByVal uReturnLength As Long, _

ByVal hwndCallback As Long) As Long

以下是打开CD-ROM的过程代码：

retvalue = mcisendstring("set CDAudio door open", _

returnstring, 127, 0)

关闭CD-ROM用以下代码：

retvalue = mcisendstring("set CDAudio door closed", _returnstring, 127, 0)

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

ShowMan

关注关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

论文翻译：2020_DARCN_A Recursive Network with Dynamic Attention for Monaural Speech Enhancement

凌逆战的博客

12-01

897

论文地址：基于动态注意的递归网络单耳语音增强论文代码：https://github.com/Andong-Li-speech/DARCN 引用格式：Li, A., Zheng, C., Fan, C., Peng, R., Li, X. (2020) A Recursive Network with Dynamic Attention for Monaural Speech Enhancem...

论文翻译：2022_PACDNN: A phase-aware composite deep neural network for speech enhancement

凌逆战的博客

02-15

1564

论文地址：PACDNN：一种用于语音增强的相位感知复合深度神经网络相似代码：https://github.com/phpstorm1/SE-FCN 引用格式：Hasannezhad M，Yu H，Zhu W P，et al. PACDNN： A phase-aware composite deep neural network for speech enhancement[J]. Speec...

参与评论您还未登录，请先登录后发表或查看评论

linux下挂载和卸载cdrom

mashuanxiang的专栏

07-07

8615

1.查询块设备及mount位置 [root@slave143 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 3.6

attention :: 怎样打开或关闭 CD-ROM (转)

cuiji1279的博客

06-25

attention :: 怎样打开或关闭 CD-ROM (转)[@more@]如果你想通过VB打开或者关闭CD-ROM，你可以向windows Multimedia DLL发出一条相关的命令请求，但是你必须先声明DL...

ESP32-S3开发实战：集成蓝牙Mesh协议栈

alpha的博客

12-04

367

本文详细介绍如何基于ESP32-S3与ESP-IDF框架实现蓝牙Mesh协议栈的完整落地，涵盖环境搭建、协议初始化、模型开发、网络部署及真实场景应用，解决多跳通信、组网稳定性与低功耗等关键问题，构建可规模化的智能照明系统。

34、FireWall-1 Next Generation: Deployment, Installation, and Configuration Guide

fun88的博客

08-11

本文详细介绍了FireWall-1 Next Generation的部署、安装和配置过程。内容涵盖了客户端/服务器架构的优势、硬件要求、安装步骤、SmartDashboard的使用、对象定义、规则创建以及策略部署。此外，还提供了最佳实践、故障排除技巧和关键配置任务的分步指南，以确保安全、高效的防火墙实施。

LLMs之Colossal-LLaMA-2：Colossal-LLaMA-2的简介(基于LLaMA-2架构+中文优化+扩充词表+仅千美元成本)、安装、使用方法之详细攻略

头部AI社区如有邀博主AI主题演讲请私信—心比天高，仗剑走天涯，保持热爱，奔赴向梦想！低调，专注，谦虚，自律，反思，成长，还算比较正能量的博主，公益免费传播…内心特别想在AI界做出一些可以推进历史进程影响力的技术(兴趣使然，有点小情怀，也有点使命感呀

09-27

4821

LLM之Colossal-LLaMA-2：Colossal-LLaMA-2的简介、安装、使用方法之详细攻略目录 Colossal-LLaMA-2的简介 Colossal-LLaMA-2的安装 Colossal-LLaMA-2的使用方法 Colossal-LLaMA-2的简介 2023年9月25日，Colossal-AI团队推出了开源模型Colossal-LLaMA-2-7B-base。这个模型是LLaMA-2的一个衍生版本，

国开计算机专业英语,国开吉林00829-计算机专业英语-形成性考核一-辅导资料.docx...

weixin_39909859的博客

06-24

527

国开吉林00829-计算机专业英语-形成性考核一-辅导资料.docx计算机专业英语-形成性考核一-辅导资料说明如果课程题目是随机的，请按CTRLF在题库中逐一搜索每一道题的答案特殊说明请仔细课程的题目每学期都可能更换，所以请仔细核对是不是您需要的题目再下载第1题 cpu stands for .a. motherboard b. central processing unit c. memory...

【USB】全球USB厂家 USB ID大全。更新时间：2017-07-29

热门推荐

shen_wei的专栏

08-15

9万+

# # List of USB ID's # # Maintained by Stephen J. Gowdy # If you have any new entries, please submit them via # http://www.linux-usb.org/usb-ids.html # or send entries as patches (diff -u old new) i

Performance Endpoint for Linux (32-bit and 64-bit) File README Version 7.30 SP1 Copyright (C) 2003-2013 Ixia. All rights reserved. Ixia 26601 W. Agoura Road Calabasas, CA 91302 U.S.A. Web: www.ixiacom.com Phone: +1 818 871-1800 or + 1 877 FOR IXIA Fax: +1 818 871 1805 General information: Email: info@ixiacom.com Technical support: Email: support@ixiacom.com Thanks! We appreciate your interest in our software. We keep seeking ways to improve it; we welcome your feedback and suggestions. We continue to enhance and expand our Web site -- come and visit us. The latest versions of the endpoints are always available for free at http://www.ixiacom.com/support/endpoint_library/ Note that the Ixia Performance Endpoints have not been tested with NetIQ applications and may not function properly with NetIQ applications. Linux kernel 2.4.20 We've tested with packages that implement Linux kernel 2.4.20. We have not tested this version of Performance Endpoint with earlier versions of the Linux kernel. Only TCP and UDP/RTP support The Performance Endpoint for Linux uses the Sockets interface to the TCP/IP support shipped with Linux. IPX, SPX, or other network protocols are not supported in this version. For IPv6 support, kernel 2.4.18-3 or better is required. Here's what you need to run the endpoint program with Linux: - A computer capable of running Linux well. We recommend a CPU such as Intel Pentium III or better. For the 64-bit (x64) version of the endpoint you will need an AMD64/EM64T compatible CPU, such as AMD Opteron or an Intel Xeon with support for EM64T technology. For the 64-bit versions of the endpoint the corresponding 64-bit version of Linux is also required. - 64 MBytes of RAM. The total RAM requirement depends on RAM usage of the underlying protocol stack and the number of concurrent endpoint pairs. For tests involving over one hundred connections through a single endpoint, additional memory may be required. - A hard disk with at least 8 MBytes of space available. - Linux kernel 2.4.20 or better. Older versions of the Linux kernel may not support IPv6 properly. TAR-Based Endpoint Installation for Linux ------------------------------------------------------------------- Use the TAR-based installation if you are installing the endpoint on any Linux platform other than Red Hat (32-bit) or SuSE (64-bit). First, make sure that you are logged in as a "root" user. Also remember all commands and parameters discussed here are case-sensitive. Use the combination of uppercase and lowercase letters as shown below (for all the file names, "M" represents the major version and "m" represents the minor version). The following instructions describe how to install the endpoint on a computer with a CD-ROM drive. Put the CD-ROM in your CD-ROM drive. If you want to install the 64-bit version of the endpoint, replace the name of the archives (pelnx_Mm.tar.gz and pelnx_Mm.tar) from the following instructions with pelinux_amd64_Mm.tar.gz Enter the following commands, assuming your CD-ROM drive device name is /dev/cdrom and you are able to create a temporary directory named cdrom: mkdir /cdrom mount /dev/cdrom /cdrom The CD-ROM contains an archive of the endpoint package. First use the RM command to ensure a clean temporary install directory. Then use the TAR command to extract the archive contents from the CD-ROM: cd /tmp rm -fr temp tar -zxvf ./pelnx_Mm.tar.gz Next, run the endpoint's installation script to install the endpoint: ./endpoint.install The license agreement is shown, presented with the "more" command. Press the space bar until the end of the agreement is displayed. You are asked whether you accept the terms and conditions of the agreement. If you do, enter "accept_license" and press return. After the installation is complete, use the UMOUNT command to unmount the file system from the CD-ROM: umount /cdrom During installation, you will see several status messages. Pay close attention to the output. When the installation is successful, you see the message "Installation of endpoint was successful." The installation script and temporary directory are not removed automatically if the installation is successful. If you need the disk space after installing the endpoint, you may delete the temporary directory and installation script. Unattended Installation for TAR-Based Linux You can install the endpoint silently, that is, without providing any additional user input. Complete the steps, as described above, through the TAR command. Next, run the endpoint's installation, adding the "accept_license" parameter: ./endpoint.install accept_license Removing the TAR-Based Endpoint Package (Uninstall) You must be logged in as the root user to remove the endpoint package. If you need to remove the endpoint package from your hard disk, first stop the endpoint program (if running). Enter the following command: /usr/local/Ixia/endpoint -k Use the following command to remove the endpoint: /usr/local/Ixia/endpoint.remove If the removal is successful, you will see the following: "Removal of endpoint was successful." This removes the files from /usr/local/Ixia, except for any files added to this directory that were not present at install, such as the endpoint.ini file, but does not delete the directory. The remove program does not automatically delete files added to the directory that you may need if you reinstall the product. RPM-Based Endpoint Installation for Linux ------------------------------------------------------------------- Use the RPM-based installation if you are installing the endpoint on Red Hat (32-bit) or SuSE (64-bit). For installation, first make sure that you are logged in as a "root" user. Also remember all commands and parameters discussed here are case-sensitive. Use the combination of uppercase and lowercase letters as shown below (for all the file names, "M" represents the major version and "m" represents the minor version). The following instructions describe how to install the endpoint on a computer with a CD-ROM drive. Put the CD-ROM in your CD-ROM drive. If you want to install the 64-bit version of the endpoint, replace the name of the RPM file (pelnx_Mm.rpm) from the following instructions with pelinux_amd64_Mm.rpm Enter the following commands, assuming your CD-ROM drive device name is /dev/cdrom and you are able to create a temporary directory named cdrom: mkdir /cdrom mount /dev/cdrom /cdrom Copy the pelnx_Mm.rpm file from the CD-ROM drive to a local directory (for example, tmp). cp /cdrom/endpoint/linux/pelnx_Mm.rpm /tmp For RPM, use the RPM command to install the endpoint: rpm -Uvh /tmp/pelnx_Mm.rpm After the installation is complete, use the UMOUNT command to unmount the file system from the CD-ROM: umount /cdrom During installation, you will see several status messages. Pay close attention to the output. When the installation is successful, you see the message "Installation of endpoint was successful." Removing the RPM-Based Endpoint Package (Uninstall) You must be logged in as the root user to remove the endpoint package. If you need to remove the endpoint package from your hard disk, first stop the endpoint program (if running). Enter the following command: /usr/local/Ixia/endpoint -k Use the following command to remove the endpoint (you must be logged in as root to run this program): rpm -e endpoint If the removal is successful, you will see the following: "Removal of endpoint was successful." This removes the files from /usr/local/Ixia, except for any files that were added to this directory that were not present at install, such as the endpoint.ini file, and does not delete the directory. The remove program does not automatically delete files added to the directory that you may need if you reinstall the product. What We Do During Installation Here is what happens during the installation steps. The endpoint is installed into the directory /usr/local/Ixia. A directory is created with the following contents: - the executable programs. - the README file. - various install and uninstall programs. - the directory cmpfiles. This directory contains files with the .cmp file extension. These are files containing data of different types, such as typical text or binary data. These files are used by the endpoint as data on SEND commands. The different data types can be used to vary the data compression performance of your network hardware and software. - the file endpoint.ini. Our software ends any copy of the endpoint program currently running and starts a copy of the newly-installed endpoint. You can run tests immediately, without a reboot. Our software displays information on how to update your system to have the endpoint start automatically upon reboot. No changes are made to the PATH environment variable of the root user. *IxChariot is a registered trademark of Ixia. United States Patent Numbers 5,838,919, 5,881,237, 5,937,165, and 6,061,725. Other patents pending.啥意思

10-16

安装步骤：包括挂载CD、解压/安装包、运行安装脚本（或rpm命令）、接受许可协议等。 7. 卸载步骤：停止端点程序，运行卸载脚本（TAR方式）或rpm卸载命令（RPM方式）。 8. 安装后的文件位置：/usr/local/Ixia，...

jackson 控制处理

x17809211858的博客

12-01

232

default-property-inclusion: always # 确保 null 会走到序列化器。

Mybatis02:核心功能

清晓粼溪的博客

12-05

484

本文介绍了MyBatis框架中的多表映射、动态SQL和插件机制。多表映射部分详细说明了"对一"和"对多"关系的配置方法，包括association和collection标签的使用。动态SQL部分涵盖了if/where、set、choose/when/otherwise、foreach、trim等标签的应用场景，以及SQL片段复用技巧。插件机制部分重点介绍了Interceptor接口实现和PageHelper分页插件的配置使用，包括分页查询的实现方式。最后提及了MyBa

【Java泛型一遍过】

2301_80170301的博客

12-05

553

核心价值：泛型是编译时的类型安全工具。关键语法：掌握泛型类、泛型方法的定义。精髓：理解PECS 原则，这是灵活使用通配符的关键。底层认知：理解类型擦除，能解释很多“为什么不行”的问题，并找到变通方案。实践：遇到类型擦除的坑时，考虑使用Class<T>对象作为类型令牌。

阿里140-n值纯算

wstc2689784536的博客

12-02

1045

阿里140-n值逆向纯算

C++STL：熟悉vector的底层实现，部分源码解析，迭代器失效和深层次浅拷贝

liriying的博客

12-05

122

对vector的底层代码深度解析，包括迭代器失效，传参与模板冲突，更深层次的浅拷贝以及部分源码解析

C# 调用 DLL为什么不像 C/C++调用 DLL 时需要lib库

luohaitao的专栏

11-30

736

C#调用DLL机制与C/C++存在本质差异：C#基于托管代码和运行时动态绑定，无需.lib文件，仅需DLL即可完成调用。关键区别在于C#完全绕过了C/C++的静态链接流程，通过两种方式实现：调用托管DLL时利用内置元数据替代头文件和.lib；调用非托管DLL时通过DllImport实现运行时动态绑定。而C/C++必须在编译期通过.lib解析符号，否则会报链接错误。在C#项目中"添加引用"时只显示托管DLL，因为VS知道C#不需要处理原生.lib文件。唯一可能接触.lib的情况是使用C++

【C++11（二）】可变参数模板和 lambda表达式

attention :: 怎 样 打 开 或 关 闭 CD-ROM

attention :: 怎样打开或关闭 CD-ROM