-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
Best OS for RC5?
- Thread starter Shack70
- Start date
sciencewhiz
Diamond Member
linux is the best, slightly ahead of nt based OSs, which are a little ahead of win9x.
Even if someone could right a client for the palm, it would suck batteries and noone would use it.
Even if someone could right a client for the palm, it would suck batteries and noone would use it.
sciencewhiz:
I'm curious in how you define "better"? Are you talking in terms of speed?
Cuz I have a win2k/RedHat dual-boot... since I am in win2k most of the time I only install RC5 client on my win2k machine and use that to crack... If Linux is faster then I may actually setup a client in RedHat and boot into RH to crack when I sleep at night 🙂
I'm curious in how you define "better"? Are you talking in terms of speed?
Cuz I have a win2k/RedHat dual-boot... since I am in win2k most of the time I only install RC5 client on my win2k machine and use that to crack... If Linux is faster then I may actually setup a client in RedHat and boot into RH to crack when I sleep at night 🙂
NotEasyBeingHappy
Member
According to me the mac(G4) is the fastest @ cracking RC5, but I god be wrong.
The OS isn't the most important thing i.e. AMD is a lot better at cracking then INTEL
The OS isn't the most important thing i.e. AMD is a lot better at cracking then INTEL
Using a K6-3 400 (66 mhz bus), here are my actuals:
linux mandrake 7.2, no gui: 691 mkeys/s
winNT 4.0: 691 mkeys/s
win98se: 690 mkeys/s
Maybe I could get more out of linux, but I'm no linux tweaker/guru.
Win98se and NT are running as bare-bones as I could get them.
These are all from the same machine...right now it has win98 and linux set up as a dual-boot; before that it ran NT. All it does is crack rc5 24/7.
On my PIII systems, win2K and win98se are pretty close in terms of mkeys/sec.
linux mandrake 7.2, no gui: 691 mkeys/s
winNT 4.0: 691 mkeys/s
win98se: 690 mkeys/s
Maybe I could get more out of linux, but I'm no linux tweaker/guru.
Win98se and NT are running as bare-bones as I could get them.
These are all from the same machine...right now it has win98 and linux set up as a dual-boot; before that it ran NT. All it does is crack rc5 24/7.
On my PIII systems, win2K and win98se are pretty close in terms of mkeys/sec.
Good luck messing with DOS nic drivers.
It can be done, but it's a real pain.
BlackFlagg, Yes, it's best to run a pproxy on your network somewhere.
Any OS with a pproxy listed will work fine.
Follow the link in my sig, and read the "Setup Page".
I've listed some do's and dont's for Klinux.
It can be done, but it's a real pain.
BlackFlagg, Yes, it's best to run a pproxy on your network somewhere.
Any OS with a pproxy listed will work fine.
Follow the link in my sig, and read the "Setup Page".
I've listed some do's and dont's for Klinux.
I haven't been able to use Klinux on this machine (k6-3 400)...I get assembly code loop at the beginning, and that's it. I figured that's because the nic isn't supported, according to KW's page (3com 905-tx). Anyway, I tried a couple of versions and could never get it to boot up.
I used dos on this machine for a while, and it was a little faster, as I recall...I didn't write it down, but I think it was 698 mkeys/sec.
I would let the dos version run for a few days, then run win3.11 and have it dump the results to my proxy. That was quicker and easier than installing the dos nic drivers.
I used dos on this machine for a while, and it was a little faster, as I recall...I didn't write it down, but I think it was 698 mkeys/sec.
I would let the dos version run for a few days, then run win3.11 and have it dump the results to my proxy. That was quicker and easier than installing the dos nic drivers.
alpha7x, did ya use the Klinux-2.2 version, and make the disk with the rawrite utility?
I've heard of some people just unzipping Klinux to a floppy, thinking that is all you need to do.
That nic should be supported.
I've heard of some people just unzipping Klinux to a floppy, thinking that is all you need to do.
That nic should be supported.
An AMD K6/3 is considered a 686 class CPU.
A 586 would be pre MMX, as in a P75 or a (gasp) Cyrix PR150.
The Klinux-2.4 versions would not recognize that CPU.
This will be taken care of in the Klinux-v.3 release, as I've combined all CPU's into each version.
The only differance between Klinux-v.3A from Klinux-v.3B or Klinux-v.3C will be nics supported.
A 586 would be pre MMX, as in a P75 or a (gasp) Cyrix PR150.
The Klinux-2.4 versions would not recognize that CPU.
This will be taken care of in the Klinux-v.3 release, as I've combined all CPU's into each version.
The only differance between Klinux-v.3A from Klinux-v.3B or Klinux-v.3C will be nics supported.
sciencewhiz
Diamond Member
Alpha, I have done those tests before also. They all benchmark approximately the same, but in actual operation, linux is the best.
For me, in normal use, Linux cracked at the same rate as was benchmarked. Win 2000 cracked at a rate of about 1 kkey/sec. Win98 cracked at a rate of about 7 kkey/sec slower than the benchmarked rate.
As you can see, there isn't much of a difference. Unless you plan on leaving it long term, the cracking time lost while re-booting is probably not worth the extra gain in speed.
When i get a chance, I will try the dos client as well, to see how it compares.
For me, in normal use, Linux cracked at the same rate as was benchmarked. Win 2000 cracked at a rate of about 1 kkey/sec. Win98 cracked at a rate of about 7 kkey/sec slower than the benchmarked rate.
As you can see, there isn't much of a difference. Unless you plan on leaving it long term, the cracking time lost while re-booting is probably not worth the extra gain in speed.
When i get a chance, I will try the dos client as well, to see how it compares.
Now, I'm confused.
The Kernel Configuration says:
- "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SX, Cyrix/TI 486DLC/DLC2 and UMC 486SX-S.
Only "386" kernels will run on a 386 class machine.
- "486" for the AMD/Cyrix/IBM/Intel DX4 or 486DX/DX2/SL/SX/SX2 AMD/Cyrix 5x86, NextGen Nx586 and UMC USD or USs.
- "586" for the generic Pentium CPUs, possibly lacking the TSC (time stamp counter) register.
- "Pentium" for the Intel Pentium/Pentium MMX, AMD K5, K6 and K6-3D.
- "PPro" for the Cyrix/IBM/National Semiconductor 6x86, MII and Intel Pentium II/Pentium Pro.
Building Klinux-v2 I used "PPro" for the 686 versions, which wouldn't support an AMD K6/3.
I used "486" for the 586 - 486 version, that would/should support an AMD K6/3 CPU.
So you're right alpha7x, the Klinux-2.4 version should of worked.
It got a little confusing trying to keep everything straight building Klinux-2 version, that I decided to generalize everything into as few different Klinux images as possible.
So when Klinux-3x comes out, every version will support all CPUs, all will have DHCP enabled in the kernel, where if you don't use it, or need it, it'll time out, and you configure your networking the way you want too.
Three versions are easier to work with (for me anyway) than eight.
The Kernel Configuration says:
- "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SX, Cyrix/TI 486DLC/DLC2 and UMC 486SX-S.
Only "386" kernels will run on a 386 class machine.
- "486" for the AMD/Cyrix/IBM/Intel DX4 or 486DX/DX2/SL/SX/SX2 AMD/Cyrix 5x86, NextGen Nx586 and UMC USD or USs.
- "586" for the generic Pentium CPUs, possibly lacking the TSC (time stamp counter) register.
- "Pentium" for the Intel Pentium/Pentium MMX, AMD K5, K6 and K6-3D.
- "PPro" for the Cyrix/IBM/National Semiconductor 6x86, MII and Intel Pentium II/Pentium Pro.
Building Klinux-v2 I used "PPro" for the 686 versions, which wouldn't support an AMD K6/3.
I used "486" for the 586 - 486 version, that would/should support an AMD K6/3 CPU.
So you're right alpha7x, the Klinux-2.4 version should of worked.
It got a little confusing trying to keep everything straight building Klinux-2 version, that I decided to generalize everything into as few different Klinux images as possible.
So when Klinux-3x comes out, every version will support all CPUs, all will have DHCP enabled in the kernel, where if you don't use it, or need it, it'll time out, and you configure your networking the way you want too.
Three versions are easier to work with (for me anyway) than eight.
Kilowatt,
Well, I know the 2.4 version doesn't work on my machine. It never boots, just scrolls. Wouldn't the "pentium" version be the one that worked on a K6-3, rather than the 486 version?
Anyway, version 3 will be great, I'm sure. Thanks for all the work you have put into klinux!
Well, I know the 2.4 version doesn't work on my machine. It never boots, just scrolls. Wouldn't the "pentium" version be the one that worked on a K6-3, rather than the 486 version?
Anyway, version 3 will be great, I'm sure. Thanks for all the work you have put into klinux!
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
