MERCURY127
Content Type
Profiles
Forums
Events
Posts posted by MERCURY127
-
-
Win31 in protected mode, likely, also cant run...
show garbaged logo, then fall in dos... instead decktop.
yes, i limit memory to 128 MB before run Win31...2 hours ago, MrMateczko said:I haven't had any issues with my GTX 1050 Ti, the standard VGA driver in 98SE worked fine...
which ur card vendor and model? my is Palit GTX 1070 Super Jetstream...
can u dump ur VBIOS from C000?
0 -
38 minutes ago, MrMateczko said:
I haven't had any issues with my GTX 1050 Ti, the standard VGA driver in 98SE worked fine...apart from the usual graphical artefacts.
What are your PC specs? Can you try the 1070/98SE on different machines?
It is strange. My machine is exactly that, as on previous years - core i7 3770, 8 Gbytes ram. I just add gtx 1070 yesterday...
0 -
34 minutes ago, deomsh said:
Is win31 Enhanced mode working with XGA (640x480 16 colors)? XGA uses the older 3.0 vga-driver.
Hmm...
640 x 480 x 4 bpp - it is VGA. XGA is 1024 x 768 x 8 bpp - very old IBM vc.
Are u sure, that talk about XGA?
0 -
also, win31 in standard mode work ok with own vga.drv.
0 -
No, and i think, this cant help - i try just remove vga.drv/vgafull.3gr/vbemp.drv/vbe.vxd from system folder, and see no diff-es.
ie, machine crashed exactly in vdd.vxd module, before loading any video *.drv.also, win2k with own standard vga.sys work ok, but vbempnt - not, have code 10.
also, this card not support any CGA/EGA graphics modes. only support VGA 640x480 x4 bits, MCGA 320x200 x8 bits, and vesa svga 640x480+ x8/16/32 bits.
ie, Alley Cat game, for sample, here is not run...here is some technical details about card:
Video Monitor Vendor: BenQ Monitor Model: BenQ BL2411 (BNQ 8011) Video Chip Vendor: Nvidia Corp Video Chip: Unknown Device VESA OEM String: NVIDIA Video Memory Size: 16 MB +-----------------------------------------+ | PCI/AGP Devices | +-----------------------------------------+ PCI/AGP PCI Bus Version: 3.0 Number of PCI Buses: 6 Bus: 01h, Device: 00h, Function: 00h Vendor (10DEh): Nvidia Corp Device (1B81h): Unknown Device Subsys Vendor (10DEh): Nvidia Corp Subsystem ID (1B81h): Unknown Class (03h): Display SubClass (00h): VGA Revision: A1h Interface: 00h Device Properties Device Timing: Fast Memory Access: [X] I/O Access: [X] Bus Master: [X] 66 MHz Speed Support: [ ] Device Resources ROM Address: F7000000h Memory Address: F6000000h - F6FFFFFFh Memory Address: E0000000h - EFFFFFFFh Memory Address: F0000000h - F1FFFFFFh Base I/O Port: 0000E000h - 0000E07Fh System IRQ: 11 Interrupt Pin: INTA# PCI-E Capabilities PCI Express Version: 2.0 Device/Port Type: Legacy PCI-E Endpoint Link Speed: 8.0 GB/s (Current: 2.5 GB/s) Link Width: x16 (Current: x16) Link Port Number: 0 Physical Slot Number: 0 Bus: 01h, Device: 00h, Function: 01h Vendor (10DEh): Nvidia Corp Device (10F0h): Unknown Device Subsys Vendor (10DEh): Nvidia Corp Subsystem ID (1B81h): Unknown Class (04h): Multimedia SubClass (03h): Hi-definition Audio Revision: A1h Interface: 00h Device Properties Device Timing: Fast Memory Access: [X] I/O Access: [ ] Bus Master: [X] 66 MHz Speed Support: [ ] Device Resources Memory Address: F7080000h - F7083FFFh System IRQ: 10 Interrupt Pin: INTB# PCI-E Capabilities PCI Express Version: 2.0 Device/Port Type: PCI-E Endpoint Link Speed: 8.0 GB/s (Current: 2.5 GB/s) Link Width: x16 (Current: x16) Link Port Number: 0 Physical Slot Number: 0 +-----------------------------------------+ | Video | +-----------------------------------------+ Video Video Chip Vendor: Nvidia Corp Video Chip: Unknown Device Subsystem Vendor: Nvidia Corp Video Memory Size: 16 MB Bus Type: PCI-E VESA OEM String: NVIDIA VESA Version: 3.0 Vendor Name: NVIDIA Corporation Product Name: BIOS-P/N@N11313 Chip Rev OEM Software Version: 134.4 VESA Power Management VESA PM Version: 1.0 Standby: [X] Suspend: [X] Off: [X] Reduced On: [ ] PCI-E Capabilities PCI Express Version: 2.0 Device/Port Type: Legacy PCI-E Endpoint Link Speed: 8.0 GB/s (Current: 2.5 GB/s) Link Width: x16 (Current: x16) Link Port Number: 0 Physical Slot Number: 0 VESA Modes Number | Mode |Resolution|Colors| bpp| Features -------+-------+----------+------+----+---------- 101h | Graph | 640x480| 256| 8| Bank + LFB 103h | Graph | 800x600| 256| 8| Bank + LFB 105h | Graph | 1024x768| 256| 8| Bank + LFB 107h | Graph | 1280x1024| 256| 8| Bank + LFB 111h | Graph | 640x480| 64k| 16| Bank + LFB 112h | Graph | 640x480| 16M| 32| Bank + LFB 114h | Graph | 800x600| 64k| 16| Bank + LFB 115h | Graph | 800x600| 16M| 32| Bank + LFB 117h | Graph | 1024x768| 64k| 16| Bank + LFB 118h | Graph | 1024x768| 16M| 32| Bank + LFB 11Ah | Graph | 1280x1024| 64k| 16| Bank + LFB 11Bh | Graph | 1280x1024| 16M| 32| Bank + LFB 145h | Graph | 1600x1200| 256| 8| Bank + LFB 146h | Graph | 1600x1200| 64k| 16| Bank + LFB 14Ah | Graph | 1600x1200| 16M| 32| Bank + LFB 14Bh | Graph | 1920x1200| 256| 8| Bank + LFB 14Ch | Graph | 1920x1200| 64k| 16| Bank + LFB 14Dh | Graph | 1920x1200| 16M| 32| Bank + LFB0 -
Yes. It is all. The End. The Great End.
No graphics. Just text message on black screen of death. Even with standard VGA driver. Even in safe mode.
Have any ideas?
0 -
Your router must be support also 2.4 Ghz b/g standards. Buy or find any old b/g pci WiFi card with real drivers for 9X. This give u up to 54 mbit/sec connect. After this, ask me for Odyssey supplicant for 9X...
0 -
Possible problems:
- Too much memory, if u see black screen with protection error - remove one 512 module;
- WiFi, for 9x not exist good drivers with 11n support.
0 -
Babelmap? Newest? On se? This?
http://www.babelstone.co.uk/Software/BabelMap.html
They wrote:
BabelMap runs on Windows 2000, XP, Vista, 7, 8, 8.1 and 10.
0 -
oh, sorry, guys
i forget say - also need set bootlogo = 0, and/or remove logow.sys, for properly work Winexit patch... else u cant see real dos prompt after win terminate.
sorry...
0 -
on my machines, 9x successfully disable all usb cntrlrs, when exit in real mode (ie for executing fdapm or winexit), but can't re-enable it, when doing second start. machine just halted.
0 -
You already can use winoff16 as Windows only (not machine) restarter, if just delete fdapm from windir.
It is will work with both 3X and 9X. But you can't do windows only restart, if using 9X with USB2 drivers!
0 -
ACPIOFF is a win.com patch (currently only for Windows 98SE), and a small 16-bit WinOff16 utility that both allow you to shutdown Windows and invoke the utility from FreeDOS, FDAPM.COM, with the POWEROFF command, which tries to shutdown the machine through the interfaces APM and ACPI.
PASSWORD: 1.
JUST 1.
Look English doc at end TXT file1 -
This dll is just placeholders. It doesn't any but return properly codes.
Try inf for sdhost bus as we doing inf for hda bus.
0 -
Hmm... Hello :)
Send me these sys and dll, or all pack, in private, I try decompile and analyze it...
0 -
why just not install dx8 redistributables?
0 -
if developer forget recompile app for release - then u may req debug versions libs...
0 -
in generic, here is two veriants building process:
DEBUG - for development. when u write own app, u use DEBUG version of ALL - windows kernel API libs, MS CRT libs, DX libs, etc. if and when u use debug libs, u can use VS internal or any other debugger at souce level, do step-by-step trace, trap exceptions, and see value any vers in properly type. its fast and cool. but these DEBUG libs contains many debug info, they big and slow, why they not include in usual windows redist.
RELEASE - when app succefully writed and debugged, u recompile it w/o using degub versions libs. then app will use only standart libs, non dev, appear lesser and faster, and also cointains NO dubeg info, which can help end user crack or revesre app...
0 -
7 hours ago, cov3rt said:
i wanted to know if one would need to install directx 8.0a sdk AND visual studio 6.0 AND the microsoft platform SDK all in the same system.
yes, but ONLY IF u want DEVELOP NEW DX8.0 Application, or RECOMPILE old DX8.0 example.
0 -
or can use FAR manager.
0 -
16 minutes ago, Tryphon said:
What do you think?
buggy or incompatible hardware.
nt and nix fair more stable and tolerant to hw errors.0 -
2 minutes ago, Tryphon said:
Is it possible that this switch to protected mode failed at the beginning knowing that I got no error message
yes, but u must see at least
[000D76BB] Loading Vxd = vkd
[000D76BB] LoadSuccess = vkd
[000D76BB] SYSCRITINIT = VMM
[000D76BB] SYSCRITINITSUCCESS = VMMin bootlog, as indication start prot mode...
after Loading Vxd / LoadSuccess (hich is real mode part)
will appear SYSCRITINIT / SYSCRITINITSUCCESS
and DEVICEINIT / DEVICEINITSUCCESS
for each vxd,
and after [000D76BC] DEVICEINIT = CONFIGMG
begin processing of device tree.
0 -
i know. but it is better do not pack anyway - more flexible and easy troubleshooting,
0 -
And... What about step-by-step loading? F8 - s-b-s, enter win, and try.
Also, what if try real debugger, for example SoftIce? ;D
0
Win9x vs GTX 1070 - VDD initialization crash, protection error
in Windows 9x/ME
Posted · Edited by MERCURY127
Ok, i just mixed XGA and 8514/a...
Anyway, XGA is not run. As with VGA and modded SVGA - i just see garbaged 3.1 logo and immediate after this - blinking cursor on black screen.
if i try WIN : (run w/o logo) then i get just blinking cursor, w/o any vmode switching.
ie all look exactly as VDD* initialization problem.