Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Wait I take that back... I couldn't get it to work... Perhaps you can put it in winimage (www.winimage.com) format? I think because I have windows 2000 it's not working the way it should.
Please let me know when/if you can do this so I can retry....
Thanks,
-Michael
0 
i'm glad to see that i am not the only one to use winzip to open up the win9x mini.cab
i also created a win3x floppy about 3 months ago so i have been playing with it for some time now. i have created it for personal use & i dont know if i would offer it for download.
Digitalfish6201, if u are having trouble with it E-mail me & i can help u out...for instance instead of using progman.exe as the shell use file manager. i suggest this because i have found that using progman has caused it to crash on newer systems, also ran into come trouble creating groups, but i found a fix for that. file manager gives easier access to files...if u have the winNT 4.0 CD-ROM goto the folder called Support. within that folder u will see a folder called Hgtool & another calles Scsitool. the Hqtool folder contains the setup files for a Hardware Query tool that runs win3x on a 1.44 floppy & the Scsitool folder contains the setup files for a SCSI interrigator tool that runs win3x on a 1.44 floppy. both of these tools were emulated by David to create his Eterna Windows Clone program.
using mini.cab gives u a more comressed version to run directly from floppy, but studying the Hqtool & SCSI interrigater will show u howto set up the mini windows to load to a RAMdrive which will allow u to add more programs & features...the version that i have created is about 1.62mb uncompressed & 900kb compressed then added to a floppy containing sys files & ramdrive.sys
again, if u are having trouble with it E-mail me i may be able to help u out...
later...
N1
0
I'm not exactly having trouble with the Windows 3.1 part of my program. I used FreeDOS 2.0.25 as my DOS, and didn't put the boot files in the right place, will fix today. Also, after installing the new version, run A:\setup.exe. The way my software works is that "SETUP" copies PROGMAN.INI,REG.DAT,SYSTEM.INI,WIN.INI,and PROGRAMS.GRP. The core of MW16 is extracted from a PKZip archive on boot. It works by extracting the core to your HDD, and then deleting on exit. MWBOOT (Program called by DOS to start decompression and initialize DOSX) and SETUP were both written in QuickBASIC 4.5 by me. I will post the source soon. Also, soon to come: An expanded MW16 which stays on HDD. P.S. If you want to extract the files for yourself, they are: MWCFG.exe and MW16B09.exe. Just extract them to C:\mw16 and when in DOS mode, type DOSX.
0
This is interesting. I also 'created' a mini windows version to run from a floppy. However mine was only about 600k (compressed) and I used it only to multitask DOS. I never did really get a stable version (which may lend itself to the inherit instability of windows 3.X). Maybe we should start a consolidated effort to get this thing working as well as possible.
Any takers?
-Michael
0
You should be able to expand the functionality by using a cascading Autoexec.bat. I have a four floppy disk MS-DOS 6.22 set that I use when I am stuck in a secure server lock-up to while away the time playing Nintendo games using Nesticle. There is almost always a machine that is down so I load the floppies into it, using a 32 MB XMSDSK RAMDISK. It saved my butt New Years eve when I spent all night protecting a network from "International Cyberterrorists". **rolls eyes** In the same way, you should be able to create a multi-disk install that would add the most important features for Win3x and memory management while keeping the number of disks to something reasonable like three or four.
0
a cascading autoexec.bat? Interesting... That way you can do whatever you want, but you never leave any trace of what you were doing because you never really install anything.. Neato, I like it.
-Michael
0
A cascading autoexec.bat is simply one that has pauses and an echo message to change disks, you use the same autoexec.bat in all of the disks so the extractions are seemless and automatic. The Partition Magic 2 disk set
does exactly the same thing. Here is an example from a disk set I use to do a quick and dirty DOS install to an already SYS formatted C:\drive. For the Nintendo set I just load the files into the RAMDISK and set Comspec for that drive letter. Usually C:\ as the machines are mostly UNIX and don't have a DOS partition.
0
Michael, i created 2 floppy versions:
1st. about 1.12 mb (not including system files), it runs directly from the floppy.
extremely slooooowwwwwww!!! but it works.2nd. 900kb compressed (using the program Disk Copy Plus v. 2.6a). once RAMdrive is loaded it unpacks itself to 1.62mb
using RAMdrive is better than running direct from floppy...
click HERE to learn more about RAMdrive...
only real trouble i ran into is that i have been unable to run DOS programs when using DOSX to load windows...maybe someone knows a way around this?
"a consolidated effort to get this thing working" well i dont know? i tried working in consolidation with the Eterna Clone Admin. but i found it much easier to go at it alone. i dont plan on making my version available to download, i will more than likely write a HowTo page so that any1 interrested can create their own version based on my template...
N1...
0
You still use Ramdrive.sys? I HIGHLY recommend you use xmsdsk.exe as a replacement for it. Much more versatile.
I know about ramdrives though, I use them for all my floppies...
I guess we will all go our seperate ways on this...
-Michael
0
i have used both xmsdsk & ramdrive.sys they both get the job done.
in truth i did not use any sort of RAMdrive until after i learned how to create a floppy version of win3x...i now use RAMdrive as my Temporary Internet Files Cache > TIF Cache #2
later...
N1
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
