
RJARRRPCGP
MemberContent Type
Profiles
Forums
Events
Everything posted by RJARRRPCGP
-
137GB limit - ESDI_506.PDR and other limits
RJARRRPCGP replied to Petr's topic in Windows 9x Member Projects
I believe it was 3.0. Because I remember seeing something on the package about it being Windows ME-compatible. -
Also see http://www.msfn.org/board/?showtopic=44388 The microcode updates supplied with original 98se only updates Intel processors and does not support AMD. I knew that already. But, I'm wondering if it's not updating the microcode because of it not recognizing the L2 cache type? Even if it has microcode information for Athlon processors (at least the pre-T-bird Athlons) Athlon processors before the T-bird don't have integrated L2 cache!! Also, which driver versions should I use for nForce2? Wow! No reply! I been noticing that people have a tendency to ignore my posts. I'm requiring some help here, because I'm lost at what to do about this. I wonder if this issue only affects a couple of benchmarks? Windows 98 SE should be faster, because of less bloat. I wonder if most games arn't affected? I remember from back in 2002, when running Nintendo 64 emulation, it felt faster than under Windows XP! It does still seem true that the following applies: Later Windows version=requires more processor power just for itself.
-
Thanks for the info. Because I was worried that I had the post-SP4 rollup v2 package file in the HF directory for nothing except for bloat!
-
137GB limit - ESDI_506.PDR and other limits
RJARRRPCGP replied to Petr's topic in Windows 9x Member Projects
I want to know if it's fine with Norton Utilities 2002. This means filling up the HDD to almost 100 percent full and then run Norton Disk Doctor and Speed Disk. Because if it is, I will use the IDE driver from Via on one of my Via-based motherboards and completely replace ScanDisk with Norton Disk Doctor! I also wonder if McAfee Utilities 3x would be fine, too? Despite being before 48-bit LBA? I love the Disk Tune defragmenter! That defragmenter is thorough with no doubt! -
But your heatsink may not be seated properly! A common mistake is to put the heatsink on backwards (especially with socket A) and not using heatsink compound. (thermal paste)
-
Horray! The Windows 2000 Pro installation process was fine after using the latest FDV fileset and the fileset you posted! No BSODs or any pop up error messages! This means that nLite isn't as stable as the FDV fileset and HFSLIP under Windows 2000. nLite isn't ready to go to final yet. Thus probably at least one more RC release before nLite goes final. Because nLite is still having issues with Windows 2000. This is bad news to say that one of the component removal options causes to Windows file system driver to crash! I dunno exactly why this occured, because the HDD didn't have any bad sectors. That BSOD I believe is a BSOD you would get if the HDD has bad sectors or the RAM malfunctioning, such as if OC'ing it too much.
-
Where? At http://www.vorck.com/2ksp4-old.html#10
-
Can HFSLIP slipstream or at least integrate post-SP4 rollup v2? FDV said that the post-SP4 rollup can't be slipstreamed!
-
What the bleep! Can't install DirectX 9.0c with 98Lite'ed
RJARRRPCGP replied to RJARRRPCGP's topic in Windows 9x/ME
I don't recommend that, because there's probably 2 different versions of files mixed! -
But it's probably better than holding down the power button or pressing the reset button, because as long as Windows was shut down by using the shutdown menu option or the shutdown Power outages and Windows crashes are the problems that are the most likely to cause Windows corruption. With the exception that on some PCs, even when shut down properly have HDD corruption. That's because the fact that not all data in the hardware HDD cache was written to the platter! command at the command prompt, file system changes will be fully written to the HDD, AFAIK.
-
Which file controls Blue Screen of Death?
RJARRRPCGP replied to JASpurrier3's topic in Customizing Windows
RSODs only exist for errors that are related to the boot loader, AFAIK. It appears that the majority of errors still are BSODs. -
This symptom can occur if the processor is overheating. In that case, it would be the motherboard shutting down, because of thermal protection on your motherboard. It's possible that PC with flaky hardware will be fine in safe mode.
-
Sounds like you're likely getting a corrupted CD burn. I hate to bring this to you, your CD-RW drive may be faulty. When a CD-RW drive I used to have was faulty, when the CD burning software would give me an error message and abort the CD burning process most of the time, sometimes I could burn a CD without any problem being detected by the CD burning software. But it was corrupted! Did you try again and check?
-
Something's fishy about this. Wonder if Microsoft was using some NT4 code in Windows 2003's DirectX?! I hope not! I know that NT4 didn't support any DirectX version later than DirectX 3x! Did Microsoft get lazy and "borrowed" code from NT4?
-
Don't empty the C:\WINDOWS\Prefetch folder, because then Windows will load things slowly! That's unnecessary garbage to say!
-
A simple personal firewall and more questions
RJARRRPCGP replied to k0jaK's topic in Application Installs
SoftPerfect Personal Firewall works fine. I never had a problem with it just blocking applications out of the blue. As long as a port being used by an application is in the allowed list. -
Did you check the event log for disk related errors? Also, go to Device Manager and check the IDE controller entries and see what the transfer mode is at. If it's in PIO mode, Windows probably downgraded it to PIO mode because of HDD corruption.
-
Check it out --> Official website Tango Icon Gallery ...hope to see some kind of 'pack' that change 9x into a tango-style desktop !!! DNS error. tango-project.org could not be found. Please check the name and try again. I dunno why this problem occured. It's fine now. Earlier today, I also had major slowness, my 56k internet connection was going at only around 19.2 kbps until I took my US Robotics 5699B PCI Winmodem out and hooked up a Zoom external serial modem. I didn't have this problem before. But when I tried that web site earlier, that error message seemed to occur fast, like it was impatient! It didn't even seem to wait long enough before saying that it couldn't be found!
-
It works fine now. Petr Still failing to respond. Timed out again!
-
Actually, with FAT32, the file size limit is 4 GB, AFAIK.
-
Memtest86 isn't based on Windows anyways, thus you will be running outside of Windows. Thus the Windows version you have don't matter unless you can't extract the disk image to make a Memtest86 CD or floppy disk.
-
The FTP server appears to be down.
-
You won't always get an error in a log. Please check the internet connection status tray icon. Does it report errors in received and/or sent? If it does, you may have a buggy modem driver or even worse, a bad modem!
-
Where can you get those? It appears that they likely stopped making those. They may only be available in SCSI! SCSI HDDs are notoriously expensive!
-
Is there a way to close port 135 on x64?
RJARRRPCGP replied to _Ramirez_'s topic in Windows XP 64 Bit Edition
Wow I didnt know that how do you go about doing that? How do you monitor what ports are open or not? Mind I am running XP Home yuck so I prob cant do that. It is only possible to list the ports/protocols you do want to accept, you can't specify exceptions. So to block a single port you would need to list the other 65533 individually. This filtering interface is more for hardening servers with specific services in controlled environments - e.g. only having TCP port 80 open on dedicated web servers. Properties of Internet Protocol (TCP/IP) in any of your network adapters -> Advanced button -> Options tab Highlight TCP/IP filtering, click Properties Configure the TCP & UDP ports you want to accept traffic on, and/or the IP protocol numbers you want to accept - note that this affects all network adapters on the system. Another drawback of IP filtering this way is that it does not take into account the source of the attempted connections, so you can't specify one rule for internal clients and another for external ones. Microsoft article on Windows 2000 TCP/IP features: http://www.microsoft.com/technet/itsolutio...vg/tcpip2k.mspx For workstation OS's the Windows Firewall is a better way of controlling which applications can act as servers, through exceptions in the Windows Firewall applet in the Control Panel. To monitor "open" ports you can use the command line "NETSTAT -ANO" and see which are in the "listening" state. e.g. Sample output from XP Pro: C:\>netstat -ano Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1580 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:3592 0.0.0.0:0 LISTENING 528 TCP 0.0.0.0:42510 0.0.0.0:0 LISTENING 364 TCP 127.0.0.1:1057 0.0.0.0:0 LISTENING 128 TCP 192.168.1.1:139 0.0.0.0:0 LISTENING 4 Alternatively you can run something like TCPView from SysInternals and it gives you a lot more detail too, in a fancy GUI: http://www.sysinternals.com/Utilities/TcpView.html Don't keep those ports open unless you require them for a server!! I can't trust unblocked ports with the internet viruses that have been going around. They can be updated to use exploits that we don't know about.