Article View: borland.public.cppbuilder.nativeapi
Article #6633Re: Device Driver / Shell Name Space extension.
From: Ed Mulroy [TeamB]
Date: Wed, 20 Apr 2005 22:22
Date: Wed, 20 Apr 2005 22:22
64 lines
3157 bytes
3157 bytes
> You cannot write a device driver with BCB... Why? . Ed > Umut Ozden wrote in message > news:42667ee2@newsgroups.borland.com... > > I'm translating the reply of "abc" to my first message: > ------- > You cannot write a device driver with BCB. Furthermore I think > that there is no need to write a device driver for what you want > to implement. > i. Use the SUBST command to map a folder to the drive letter F: > ii. Check this folder regularly and if a file exists in this folder > send > this file > to the external device through the COM port. > iii. Delete the file after the transfer ends. > > "abc" also suggests putting the SUBST command into a batch file and > executing this batch file automatically when Windows starts. So, a > drive letter F: will always be available when Windows starts. > ------- > I've already written a program that opens a file and sends the file > through to COM port. > Using the SUBST approach requires another program (or an extension > to > my program) that is responsible for checking regularly the related > folder > and sending a file > through the COM port to the external device, but it doesn't make > much sence > because I can already transfer a file after executing a program - my > program. > > I don't know the details of the Shell Namespace Extension approach > although > I > had a short look at the MSDN. > My scenario is: > As soon as the user attaches the RS-232 cable to the computer (at > the other > end > it is attached to the RS-232 port present on the external device) a > drive > letter F: > should appear in Windows Explorer and when the user drag&drops a > file to > F: the file should be sent through the COM port to the external > device. > > So, can Shell Namespace Extension provide what I need? In other > words, do I > have to execute my program which includes Shell Namespace Extension > after > each Windows session? I'm confused because I've seen some registry > updates > in > the related MSDN document and that makes me think that I have to > execute my > program (Shell Namespace Extension) only once to see a drive letter > F:
Technical Details
Message-ID:
<4266d64a@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<426510b2@newsgroups.borland.com> <42653759$1@newsgroups.borland.com> <42667ee2@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,2e7879eaf2f7cc70 X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Ed Mulroy [TeamB]" <dont_email_me@invalid.com> Newsgroups: borland.public.cppbuilder.nativeapi References: <426510b2@newsgroups.borland.com> <42653759$1@newsgroups.borland.com> <42667ee2@newsgroups.borland.com> Subject: Re: Device Driver / Shell Name Space extension. Date: Wed, 20 Apr 2005 18:22:50 -0400 Lines: 66 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 12.161.27.73 Message-ID: <4266d64a@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1114035786 12.161.27.73 (20 Apr 2005 15:23:06 -0800) X-Authenticated-User: edmulroy Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail