Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Drive letter
Message
From
21/05/1998 06:38:52
 
 
To
19/05/1998 10:27:34
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00099536
Message ID:
00100745
Views:
47
>>>>How would I access files on a win95 machine through a bootable Win95 Diskette? This is my exact need.
>>>>
>>>I've created such diskettes already; they even contained dual boot, for Win95 and Netware 2.12 (!). It took some 3.11 files, though it would probably work with w95 versions. I can dig up a list of the settings, if necessary.
>>
>>The Novell setup will be of limited utility; MSNetworking, needed to access Win95/WinNT peer-to-peer networking, needs an NDIS driver and protocol layer; loading the Novell layer won't do much if anything other than eating up conventional memory.
>>
>>If you need to access Novell severs as well as MSNetwork resources, you'll need both - I'd suggest looking into a multiple protocol driver and the current NetWare DOS driver distribution set for a starting place. It's going to eat up a tremendous amount of conventional RAM, so I'd recommend using HIMEM.SYS and EMM386 (or better, one of the third party memory managers like QEMM or NetRoom) to load as much of the networking stuff into UMBs and XMS as you possibly can.
>
>
>Sorry, I wasn't clear enough - under "dual boot" I meant a start menu (in config.sys), so they boot a chosen network client, not both. It's just a temporary solution, until I kill the old server.
>
>Though, I have tried to load both, but to no avail. Probably the way to go was to load both stacks from W311 instead of trying to load ipx and netx. Nevertheless, I wasn't too sorry for the failure - the old server is surely doomed.
>

Rather than NETX, I'd switch to using the VLM drivers, which can and do load into XMS; it should reduce the conventional RAM and UMB footprint somewhat, and gives you more granular control of what functionality is included on the station, so that unneeded support modules won't be loaded (further reducing the size of things.)

I assume you're already using the ODI driver sets.

>QEMM is one of my favorite pets :)

I like it, too, but I was not unhappy to see it go away. For network stuff, Helix's NetRoom was a better choice in many cases than QEMM.

Ed
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform