Would you mind fishing that code out for me? I'd be curious to take a look at it. Always found it neat when C64 hackers created their own drivers/enhancements for the 6502- I wasn't aware that the same thing (creating makeshift solutions to hardware limitations) was done for the IBM PC (aside from software companies looking to sell a product of course).
- VCF South West - June 14 - 16, Davidson-Gundy Alumni Center at University of Texas at Dallas
- VCF West - Aug 2 - 3, Computer History Museum, Mountain View, CA
- VCF Midwest - Sept 7 - 8 2024, Schaumburg, IL
- VCF SoCal - Mid February 2025, Location TBD, Southern CA
- VCF East - April 2025, Infoage Museum, Wall NJ
-
Please review our updated Terms and Rules here
On drive overlays and cloned images
- Thread starter Old Thrashbarg
- Start date
Would you mind fishing that code out for me? I'd be curious to take a look at it. Always found it neat when C64 hackers created their own drivers/enhancements for the 6502- I wasn't aware that the same thing (creating makeshift solutions to hardware limitations) was done for the IBM PC (aside from software companies looking to sell a product of course).
Chuck(G)
25k Member
View attachment BIGDISK.ZIP
Okay; this basically allows you to take an entire disk or part thereof and create any sort of logical drive with it. Coded with WD1003-type controllers in mind.
Looks like I uploaded this one in 2010 also, so it's a dupe.
Okay; this basically allows you to take an entire disk or part thereof and create any sort of logical drive with it. Coded with WD1003-type controllers in mind.
Looks like I uploaded this one in 2010 also, so it's a dupe.
Shadow Lord
Veteran Member
Okay, but how does it know about the network? I.E. How does it communicate with your particular NIC, knows where the networked HDD is, etc.? That is the part I find confusing. It seems to my uneducated mind that you need some sort of driver/program that allows the redirector to communicate with your particular HW. Or am I totally missing something?
Chuck(G)
25k Member
I think you're thinking that the "network redirector" facility in DOS is somehow inextricably linked to actual physical networks. All it provides is a "back door" if you will, into DOS's file system functionality. If you want to attach an actual network protocol to that with NICs, or other external interfaces, fine--you have to provide the details of the transport protocol and physical device drivers.
That's why, for example, under DOS, the physical device driver is loaded first (usually in CONFIG.SYS) and then the protocol layer is installed (usually at AUTOEXEC.BAT time) after DOS has been loaded. So, for example, you have an IDE/SCSI/whatever device driver for a CD-ROM, and then MSCDEX that ties into the device interface. It's MSCDEX that hooks into the DOS network redirector.
That's why, for example, under DOS, the physical device driver is loaded first (usually in CONFIG.SYS) and then the protocol layer is installed (usually at AUTOEXEC.BAT time) after DOS has been loaded. So, for example, you have an IDE/SCSI/whatever device driver for a CD-ROM, and then MSCDEX that ties into the device interface. It's MSCDEX that hooks into the DOS network redirector.
Shadow Lord
Veteran Member
Okay, I am following you now (I think).
When I read this
in your earlier post I thought you were saying you would have a terabytes of drive storage available on the network to DOS applications (e.g. from a NAS, or file server). However, I think what you were saying is that you would install a large ("terabyte") drive in the computer and provide access to it using the network redirector service instead of an overlay program like SpeedStor. Does that sound about right?
When I read this
in your earlier post I thought you were saying you would have a terabytes of drive storage available on the network to DOS applications (e.g. from a NAS, or file server). However, I think what you were saying is that you would install a large ("terabyte") drive in the computer and provide access to it using the network redirector service instead of an overlay program like SpeedStor. Does that sound about right?
Chuck(G)
25k Member
Well, that was the gist of the basic message.
With that being said, I have no problem talking to a couple of terabyte drives on a WinXP server using NetBEUI with a DOS system.
With that being said, I have no problem talking to a couple of terabyte drives on a WinXP server using NetBEUI with a DOS system.
Caluser2000
Banned
Are you using MS network client Chuck or something else? NetBEUI doesn't get mentioned that much but I've found it useful at times.
Wonder how the OP got on? Haven't heard back on progress good or bad yet.
Wonder how the OP got on? Haven't heard back on progress good or bad yet.
Chuck(G)
25k Member
On some of my older systems, yes, but that doesn't have anything to do with hosting big disks. I really have only two options--NetBEUI and ftp. I'm not aware of any other common protocols between old versions of DOS and modern gear.