awkduck
Content Type
Profiles
Forums
Events
Posts posted by awkduck
-
-
@Damnation It was suggested to me, that I search SweetLow's user name on google. If you search the forum, be sure to use the name with USB or USB 2.0; not USB2.
0 -
When Windows is running, check help/about. There you may find that Windows is already running in "Enhanced Mode". If it isn't start Windows with "WIN /3".
Start PTKMUX.EXE like this "PKTMUX 5 90". "5" is for how many different programs will need to network access at the same time. "90" is for the interrupt your driver is using (0x90). Then run PKTDRV.EXE inside a Windows Dos prompt. In that same Dos prompt run the application you want to use. I am pretty sure you can also use PKTDRV.EXE as an alternative to WINPKT, for use with Trumpet. Just run PKTDRV before you start Trumpet.
0 -
I think(?) Trumpet came with WINPKT. But if Trumpet 3 did not provide it, you can get it from this zip file "WINPKT.COM". But I don't ever remember needing an extra program like that.
You would add "WINPKT.COM 0X90" to "AUTOEXEC.BAT".
This issue might be that Trumpet needs to know the interrupt of your "packet driver". I can't remember how Tumpet 3 managed that. Maybe a ini file? Something like TRUMPET.INI? Did it ask during installation?
Bypassing the 30 day evaluation of Trumpet is something beyond the scope of this forum.
With that in mind, you might end up wanting to uninstall Trumpet 3 and install Trumpet 2, which comes with "WINPKT.COM".
Sorry, I had forgotten about the trial period.
Note: Run Win3x in enhanced mode, for best support.
Also, an alternative to "WINPKT" is "PKTMUX". "PKTMUX" is useful if you want to use multiple Dos only networking programs, in Desqview or Windows without winsock support. When you don't need winsock, you don't need to load Trumpet.
0 -
My version of Virtualbox (4.x) is very old. So I don't have much to reference with. I would look over the Virtualbox networking settings. Maybe try switching between NAT and Bridge.
0 -
Are you running this in DosBox or a VM? Unless your network is under really heavy load, a 10 second timeout should be plenty of time.
According to the output, locally things are working.
0 -
I have a couple of relatives that used to make a living programing PLC production lines. One of them leaned more towards the GUI. I guess he still does it.
1 -
MDGx has some example autoexec.bat/config.sys configurations you can examine. If you have Dos6X you can read here. For Dos7X here.
Pay extra attention to "LOADHIGH", "DEVICEHIGH", "HIMEM.SYS", "UMBPCI.SYS", and maybe "EMM386.EXE". If "UMBPCI.SYS" work for you, then you probably don't need "EMM386.EXE". But if it doesn't work, the maybe use "EMM386.EXE" with the noems option.
If you don't mind, what is the end goal?
0 -
The download should come with a SAMPLE.CFG file. Copy it and rename it somewhere like "C:\MTCP.CFG".
Then add "set MTCPCFG=C:\MTCP.CFG" to "autoexec.bat", above/before anything related to your packet driver or the mTCP application you are running.
The SAMPLE.CFG, or whatever you renamed it to, has basic settings for you network and mTCP applications. You edit SAMPLE.CFG and provide the interrupt of you "packet driver". Your packet driver is at interrupt "0x9" (as shown above). So in SAMPLE.CFG you would find "packetinit 0x60" and change it to "packetinit 0x9", or maybe "packetinit 0x90". The DHCP settings appear at the bottom of the SAMPLE.CFG file. If it is blank, then when you run DHCP it will automatically put the setting in there. If you want a static network setup, then you can put your own setting in there. With a static setup, you do not have to run DHCP; because programs will use the settings you saved.
Remember, this is just to test that things are working. This way you know things do work.
0 -
How much conventional memory do you have available?
QuoteC:\MEM
or
C:\MEM /C
0 -
I'm not sure if it works that way. It has been a long time. I remember having problems getting connectivity through the Windows Command Prompt. I think instead, I used EnhancedDrDos/TaskManager and Desqview with a packet driver muxer.
I have used Dos TSR in Windows. But it is hit and miss. Some are a roll of the dice, every time you access them.
Try your packet driver with the MTCP programs. If that works, you have a start.
For Windows, it might be better to use programs that rely on winsock.
If you have Win3.11, then you can get Trumpet TCP/IP.
But if you have WfW3.11 you can use MS's TCP/IP stack. But you may need to find a NDIS driver for you network device; or a "Packet Driver" to "NDIS" shim. Trumpet also works with WfW3.11.
Perhaps with WfW3.11, Win32s, and MS's TCP/IP stack, you can use some 32bit Win9x command prompt networking tools. Although, if you can find them, there are plenty of Win16 command prompt networking tools.
I guess it depends on what your end goal is.
If you go the Desqview and Packet driver muxer route, you can run multiple Dos windows and even run "Standard Mode" Win3x inside a Desqview windows. Then maybe you can have Win3x use Trumpet. Even WfW3.11 can run in standard mode, if you know how to do it.
0 -
@Joaquim The "SET BLASTER=" command, in autoexec.bat, is only good for games that examine autoexec.bat for the settings. I personally, have never used one that needed it. But I have been told some do. Otherwise, both SBlaster Emulation and VDMSound set the values by themselves. Many games check the environmental variable %BLASTER% to find out what setting are needed.
When running in pure Dos, having "SET BLASTER=" in "autoexec.bat" is the only way the variable gets set.
So often, when running in Windows, the setting isn't really even needed.
0 -
1 hour ago, justacruzr2 said:
Ooops! Correction. KS means Kernel Streaming.
I'll take either elaboration, as long as your sound is working :)
0 -
You can run scandisk from Dos.
During boot, press the "F8" key and select "Command Prompt Only".
Then type:
QuoteSCANDISK
Have you set (P)ATA compatibility in BIOS? Or have you already installed a SATA driver?
Beyond this, you might wait around for another person's suggestion.
But for me, I usually delete all devices out of "Device Manager", to eliminate any possibility of an issue there.
You can back-up your registry first. That way you can restore it later, and still use this Windows in the old computer.
Again, from the "Command Prompt Only"
Change directory to "C:\WINDOWS", if already not there. Then do the following:
Quoteattrib user.dat -r -a -s -h
attrib system.dat -r -a -s -h
copy user.dat user.bak
copy system.dat system.bak
If you need to restore the old registry:
Quoteattrib user.dat -r -a -s -h
attrib system.dat -r -a -s -h
del user.dat
del system.dat
copy user.bak user.dat
copy system.bak system.dat
Delete "C:\BOOTLOG.TXT" and "BOOTLOG.PRV"
Then delete everything out of "Device Manager", and boot Windows Normally.
If you can run "Regedit", you could instead delete the key "HKEY_LOCAL_MACHINE \Enum", and restart Windows normally.
Before Rebooting, it might be a good spot to install rloew's SATA patch/driver.
If Windows manages to startup, it should start detecting your hardware. If the machine locks up, it is important to take note of the current device type being detected. Sometimes this doesn't help, as it locks up before listing the device.
If Windows does actually load, but does not detect new devices, you can open "Device Manager" and click the "Refresh" Button.
If Windows does not load, or locks up during device detection, you could examine and post your new "Bootlog". It is not guaranteed to provide the answer. But it might help.
0 -
@GUS Were you able to resolve things, with access to safe mode?
0 -
On 1/10/2023 at 7:34 PM, Joaquim said:
damn... again... i fail on installing the NTFS drivers
"Free Paragon NTFS for Windows 98" seems to work, for me.
0 -
You've tried before, on a previous install. You can read about it on Sierra Help.
After you've installed it, and followed the directions, you will need to run DOSDRV.BAT from a command prompt window. From that same window you can go to the directory of your game, and run the executable that starts the game. There is another batch file that disables VDMSound. But this will also disable any sound you normally had under Windows SBlaster emulation. You might be able to reset the SBlaster environment for your card, to enable normal emulation again. I've never tried. For certain, a reboot sets everything back to normal.
To fix the "Tip of the Day" issue, create a .reg file with this contents:
QuoteREGEDIT4
[HKEY_CURRENT_USER\Software\Freeware\VDMSound]
"NextTip"=dword:00000000
"TipsFile"="C:\Program Files\VDMSound\VDMSound.tips"
"ShowTips"=dword:00000000Then double click on it, and click yes.
0 -
Can you provide more information on the hardware used?
This has happened to me, but it was an issue related to the harddrive controller.
Did this happen after/during a fresh install? Or after using the system successfully for a time?
Perhaps if you have a good bios you could set it for ATA compatibility.
0 -
5 hours ago, Joaquim said:
i need fix the audio parameters for use them on autoexec.bat
The SBlaster emulation automatically configures itself. You can run command.com and type:
QuoteECHO %BLASTER%
On one of my machines I get "A220 I5 D1 T4 P330" as a result. Since some games check the autoexec.bat for this information, you would add it like this:
QuoteSET BLASTER=A220 I5 D1 T4 P330
This only help for games and software that do not check the %BLASTER% environment variable.
Sometimes using a WDM driver provides better results for SBlaster emulation. It seems to just depend on the games and audio chip. On one of my machines the VXD SBlaster emulation provides no sound at all, with Wolf3d. Where the WDM SBlaster emulation provides me with sound effects, digitized sound, but no music. I can use Wolfdosmpu/wolfmidi to get the music. But no other sounds, unless I set effects to PC Speaker. But it will lag unless I disable everything but music.
The only way I have gotten everything to work, on that sound card, was by using VDMSound. There is an older version (1.3.3) of ECWolf that works fine with Win98. So you might consider that an option. However that only solves the issue for Wolf3d and SOD.
5 hours ago, Joaquim said:i fail on installing the NTFS drivers
I haven't tried using NTFS yet. I plan to, if I can't get Win98 reading Ext3 partitions. Hopefully someone with provide that info. If I get a chance, I'll format a pendrive and do some tests.
1 -
1 hour ago, Joaquim said:
so i win more experience
Sounds good.
I've forgotten the model number of your laptop. Could you share that again?
1 -
Are you trying to duplicate some of the progress you've made before? Or are you trying to get alternative strategies, to the ones you've previously received?
0 -
@justacruzr2 Could you message me the contents of the wdma_int.inf file? Or maybe upload it somewhere? I don't think the forum would allow it, since it is part of a commercial product.
wdma_int.inf is the inf for your card. And putting it in the inf folder should work. You could test by putting wdma_int.inf, and all of the files for, it into a new folder folder. Then install it manually by directing "Device Manager" to install a driver from the new folder. You may first have to remove the wdma_int.inf file from the inf folder and remove the "non working" device from device manager. If wdma_int.inf has the ID VEN_8086&DEV_2415&SUBSYS_3151109F&REV_02 in it, Windows will pick it and install the driver.
Unless the Millennium inf files for KS and wdmaudio have the exact same contents, as the ones from Win98, you should remove them and use the ones from Win98. The inf files contain all of the registry info you need. You should not need to enter them yourself. If the inf files provides different instructions for registry entries, between ME and 98, then you might be causing yourself a problem. If not, then it probably doesn't matter. Just something to keep in mind.
I understand that you may already know all of that. So it may be redundancy for the sake of thoroughness. You may very well be capable beyond the suggestion you've received. If it is redundancy, it is just to help get everyone on the same page.
There is a very small chance that the driver isn't compatible with Win98. It does happen that, from time to time, a driver from ME isn't meant for 98. I doubt this is the problem. If it is, rloew's Wdmex might fix the issue. I was able to get a driver that was compatible with Win98SE, but not Win98FE, working on FE that way. You can get Wdmex here.
0 -
2 hours ago, shelby said:
If it is in the device manager. Anyway TweakUI do the same job if you have or not floppy
That is true. And disabling the controller in bios isn't always an option. I've had a thinclient that had floppy support in the S.O.C. but no pinout on the board. The bios page was very basic. But at least the controller was listed in Device Manager.
Glad you found a fix. Tweak UI is an option in most Win9x unofficial service packs. I myself, don't care for it. It seemed not to correctly undo some of it's own settings. And sometimes it would try to change something that had already been changed, by me or another program. The result also caused issues reverting the change.
Until I learned how to remove "Network Neighborhood" from the Desktop without it, that ended up being all I trusting it for.
0 -
Well, I today I can't download anything from them. So I was right and "now" partly wrong. It must be a server maintenance thing.
I was going to see if the VEN/DEV/SUB/REV in the inf file matched better then the one I shared with justacruzr2.
On 12/27/2022 at 10:12 PM, justacruzr2 said:I found 3...KS, wdmaudio and wdma_int. I think the _int in wdma_int stands for Intel. This inf doesn't exist in 98SE's Inf directory. So after renaming 98SE's KS and wdmaudio (so I don't lose them), I copied all 3 over from Millennium to 98SE
In messaging I mentioned that wdmaudio.inf and KS.inf are Windows 98se Specific. So maybe replacing them with the originals allowed wdma_int.inf to work. Today I downloaded and examined a wdma_int.inf, it is definitely the inf for the card. I'm hoping the issue was resolved.
0 -
7 hours ago, Goodmaneuver said:
It could be listed different in servers of different countries. Also you need to click on Download Now button where an acknowledgment of not a robot popup will need ticking. If still a problem then try a search for Fastfame A2.71_ALC201A Driver Download (Official). The use of a VXD driver though will need to be a manual install not an auto install, directing install to the Win9x folder only.
It gets past the captcha robot acknowledgement . It says "Your download will start in a moment", "If it doesn't restart the download."
But it also does nothing when I click the restart. Since I can still download other drivers, from them, I'm wondering if it is just that driver that is down. But if it is still active for other people, it would be pretty strange.
0
Windows 98SE From USB?
in Windows 9x/ME
Posted
What happens when you install the USB drivers for Windows?
Booting Win98 from USB uses BIOS to provide the USB drive as drive C:. When you install USB drivers, it will cause problems.
So, you could just never use USB.
But if you have enough memory,
- You could setup Win98se on the computer, drivers and all
- Reduce it in size, unless you have a lot of memory
- Create a harddrive img or vhd file large enough to hold your Windows install.
- Use Virtualbox or something to make the harddrive image a system disk, using a Win98 floppy image. (Create one from your install, if you installed any update that modified MsDos 7 Boot files.)
- Copy you Windows installation to the harddrive image. (Do not overwrite MsDos 7 boot files.)
- Format your USB drive as FAT32.
- Install Grub4Dos to the USB drive.
- Then configure Grub4Dos to enable USB support and boot the Win98 harddrive image from memory.
Every time you shutdown any changes will be lost. You can get around this by installing the HxD hex editor, and using it to copy the entire drive image to a new file. You do this "while" Windows is running. Then you swap the saved image with the new one you just created. You do this before shutdown or reboot.
Some changes try to reboot Windows when they are finished. Like installing DirectX. Most of the time you are given a prompt, with an "OK" button. Run HxD and save the image before clicking the "OK" prompt. If you are given no prompt, you'll need to modify your harddrive boot image to start in Safe mode, on next boot. Then boot the harddrive image in VirtualBox or something. Finally, install whatever caused a reboot without prompting you first.
As an additional tip, use or create portable applications. Also install those portable application to you USB drive, not the Windows harddrive image. That is, unless you have a huge amount of memory. You'll want to set a permanent drive letter for you USB drive, from the Drive's "Device Manager" properties.
You'll probably want to move the default Windows and Dos temporary folders to a folder on the USB drive. Again, you'll want to assign a permanent drive letter to your USB drive
You'll also have to decide if you want you Virtual memory enabled or not. It saves room on the harddrive image if you disable it.
Drive C: will be running in "Dos Compatibility Mode". But it won't really matter.
If you get a warning about your boot sector potentially being infected/corrupted, it is because you booted the image by it's partition and not as the drive. Nothing is wrong. Grub4Dos creates fake boot data to initiate the boot.