Release-Dependent Filenames for Device Drivers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Device drivers face filename access conflicts and lockup issues during upgrade and installation processes due to lack of a uniform, conflict-free method for assigning filenames.
Innovation Solution
A method for providing release-dependant filenames for device drivers by using configuration information and a table of component files, encoding module name, version numbers, date, language, and OEM information into filenames, and employing scripts and a preprocessor to convert filenames, ensuring unique names for simultaneous operation of multiple driver versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If device drivers use standard filenames during upgrade and installation, then installation process is simple, but filename access conflicts and system lockup occur
Solution Approach 1:
The patent segments the filename into multiple distinct components: base name, version identifier, and timestamp. This segmentation allows each component to serve a specific function - the base name identifies the driver type, the version identifier tracks releases, and the timestamp prevents conflicts during simultaneous operations, thereby eliminating filename access conflicts while maintaining installation simplicity
Solution Approach 2:
The patent changes the filename parameters by incorporating version numbers and timestamps as variable components. Instead of using static filenames, the system dynamically generates filenames with unique parameter combinations, ensuring that each driver installation has a distinct filename that prevents access conflicts and system lockup
2Adaptability or versatility
If multiple versions of device driver are installed, then driver versatility is improved, but filename conflicts cause access issues
Solution Approach 1:
The patent applies preliminary action by pre-assigning unique filenames to each driver version before installation occurs. The version identifier and timestamp are embedded in the filename during the build process, so that when multiple driver versions are installed, they automatically have distinct filenames that prevent access conflicts, eliminating the need for complex file management during operation
3Adaptability or versatility
If manual filename management is used, then flexibility is maintained, but human error and operational complexity increase
Solution Approach 1:
The patent implements self-service by automating the filename generation process. The system automatically combines the base name, version identifier, and timestamp to create unique filenames without requiring manual intervention. This self-service approach maintains flexibility in filename structure while eliminating operational complexity and human error associated with manual filename management
Data Source
AI summary
A method for providing release-dependant filenames for a device driver, by providing Config information and a table of the driver's component files; assigning unique, release-dependant filenames for the component files; and producing the device driver containing the release-dependant filenames. Scripts and a preprocessor are used to convert filenames and template filename references into actual names. Name conversion comprises converting by a preprocessor for compiled files and converting by scripts for other files. Unique names of files enable simultaneous operation of two versions of a device driver. Methods include encoding module name, version numbers, date, language, and OEM information into the filename; one alphanumeric-character version number and two-character language code; configuration file and automatic generation of Config information; printing device driver with major and minor version numbers; and date encoding for files that are updated more frequently than version updates.