Content Type
Profiles
Forums
Events
Everything posted by awkduck
-
Yes, you put an I.P., that is on your network, in place of "localhost". Click Start, wait a few seconds, and then click Stop.
-
As a test, before loading into Windows, you could use mTCP Ping. If that works, you could load into Windows, not start Trumpet, and then run mTCP Ping; in a MsDos Prompt. If that works, load Trumpet and use it's Ping. If they all work, check the D.N.S..
-
Yeah, I forgot. The range is 0x60 to 0x7F. Your last setup looks good. I tested it last night. I would use the Trumpet Ping program, to ping your gateway. I guess I've had a packet driver that could only go to 0x74. So not all things are equal.
-
@Joaquim Vitrual Memory = Pagefile/Swapfile
-
@UCyborg Thanks for the keen recognition skills
-
This is in the readme.txt file, The resolution of you image was too low, I couldn't make out the error message. It seems like many of the "Acer Aspire 1690" series laptops only came with 80GB harddrives. I did see some review labelled 1690/1692 that mentioned a 160GB harddrive. Is your drive only 80GB?
-
@shelby Okay, I've tested it on a real machine. This is what I've had to do. Part of my autoexec.bat I didn't check to see if everything loaded high, but it caused no problem. You can probably REM out DHCP. The settings are saved to your mTCP config file. That way you don't use a PKTDRV for it. Just load the one for Windows/Trumpet. Now, if you've already setup a vector (interrupt) for Trumpet, you can enter the Trumpet folder and edit "TRUMWSK.INI". Find "vector=XX" and delete whatever is in there, unless it is the interrupt PKTDRV used. I mention this because with the wrong vector/interrupt Trumpet did not load for me. I had to delete that setting first. Leave the "vector=" part. Start Trumpet and then select File > Setup. You need to add a static I.P., your D.N.S. (or any usable D.N.S.), select the Packet driver dot/bullet, make sure the vector is correct, add your netmask and finally your gateway. Then click okay and restart Trumpet. Run Opera to check for connection at Google. Then open MsDos Prompt and run PKTDRV. change to the directory of Links and run it. It will fail the first connection type attempt, but when it changes to DHCP it should connect. Your screen will look blank with a block mouse cursor. Press the "G" key and type google.com > enter key. There is probably a way to skip the first Links connection type. But I didn't read the manual :) Also, I think Links has a Graphical mode, instead of text only. That would be in the manual too.
-
To run Cutemouse, run ctmouse.exe. shelby, I've noticed that your packet driver isn't in autoexec.bat. There is nothing for PKTMUX to use, without a packet driver. If I get a chance, I will post the description of a working setup.
-
You could try CuteMouse. I myself, out of curiosity, would like to see your whole autoexec.bat and what happens when you run Trumpet. But only if you feel like obliging me this. I will not be offended, if you wish only to stay on your current task.
-
User rloew created several patched for Win9x. He was/is a 9x saint. You can get his 137GB patch at the Memorial site or Retro System Revival. You don't need the patch, if your harddisk is under that size.
-
Actually, Tripredacus has a good point. I missed that you only posted your free harddrive space. The is a patch for drives over 137GB.
-
What dos mouse driver are you using?
-
Like jaclaz has said, it can be done that way. Again, like in that video, do not install your USB drivers.
-
Do you have another computer you can install this game on?
-
How many hardware/vendor I.D.s are listed in you audio card inf file (wdma_int.inf)?
-
If you can install something else, without a disk space error, then you do not need a patch. Have you googled to see if this is a common error? You could install the game using a VM with Windows. You would save your registry to a file, before install. Save it again after install. Then use Windiff to compare the two. The results can be saved to a .reg file, with REGEDIT 4 at the top of it. Copy the game files over, to the same location as on the VM. Then double click the .reg file.
-
It looks like the maximum channels is 8. It might be useful to see you full boot, to see why no packet multiplexer is found. When you used Dillo, was it fullscreen (ALT+ENTER)?
-
Does it give you an output that says that? Or can you only load 2 instances of PKTDRV? I doubt free memory is the issue, but it might be. If that is the case, sometimes TSRs can be loaded high.
-
It has been suggested that Opera and Netscape are the best Win3x era browsers. But Links and Dillo are newer. There is also MicroWeb.
-
Other considerations, with live harddisk images of Win98. You can also use a Fat16 formated disk image. Then you can used DoubleSpace with extreme compression. Afterwards, you could create a smaller Fat16 image for the smaller footprint. The disadvantage is that, the live image runs over INT13, in "Dos Compatibility Mode". This means that Windows cannot relocate DoubleSpace to higher memory. In turn you would have less conventional memory. This might not be a problem, unless you run Dos games that need plenty of conventional memory. Alternatively, you can use UPX to compress Windows EXEs and DLLs. You will want to avoid the folder with dos EXEs (Scandisk etc.). Then will not work after compression. You can create a folder on the USB drive, to keep Windows cab files. This also means cab files from updates. That would also reduce the harddisk image footprint. -To add more a persistent state- Keep wallpapers in a folder on the USB drive. I name one Wallpaper.xxx and set is as the Windows background. Now when a different wallpaper is desired, in can just be names Wallpaper.xxx (BMP/JPG). Which ever image format used, would need to adhered to. Created a batch file, on the USB drive, for start up applications. Then placed a shortcut, to it, inside the Windows startup folder. For any portable applications create a folder, on the USB Drive, with Start Menu like shortcuts and folders inside it; something like Portable Apps. Then add a command, to the startup batch file, that copies the folder to the Windows Start menu folder.
-
If you are using PKTMUX, the you should be able to let go of WINPKT. Once when you ran Trumpet without WINPKT, it output that it could not find WINPKT or PKTDRV. WINPKT is not multiplexing for the Dos Prompt. It only multiplexes for winsock. With Trumpet 3, I believe, PKTDRV can be used instead of WINPKT. But if that is not the case, then you would need to run PKTMUX and PKTDRV before WINPKT. Also, PKTMUX has not been given your "packet driver" interrupt, or quantity of needed packet driver channels. Maybe this might work? The only thing I can't remember for sure, is if you set PKTMUX packet channels to 10, can you run PKTDRV 10 times right away; making them available when needed? Or, do you have to always run it directly before the next application? If I remember correctly, if you have a bunch of PKTDRVs running, PKTMUX will direct application use to the next open PKTDRV. When ever an application times out, after use of PKTDRV, it will resets to open; ready to be used again. If for some reason a PKTDRV does not reset, there is a PKTDRV switch "/r" that will force reset. I haven't looked through PKTMUX.DOC completely, lately. There might even be a switch to tell PKTDRV how many channels to run. That doesn't ring any bells, but maybe?
-
I thought of another option. You could use a USB add-on card or PCMCIA. Then you could have the bios booting USB host disabled in Windows. But the add-on USB would provide you with active USB support. It isn't pretty, but it would be easier.
-
If it does, you've certainly earned it.
-
Have you tried? The PKGMUX.DOC (which is really just a txt file) says, This files is included with PKGMUX. There is lots of good information in there. It is easier to use Trumpet. But even if you want to use WfW3.11 and the Wolverine TCP/IP stack, you can still get away with it. You just need to use a "packet driver" to "NDIS" shim.
-
You need to change PKTMUX to interrupt 90. It is at 80 in the screenshot. Make sure you run PKTDRV before you run DHCP. You need to run PKTDRV before you run any program that needs the packet driver.