A Computer hardware and components forum. ComputerBanter.com

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » ComputerBanter.com forum » General Hardware & Peripherals » Homebuilt PC's
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Ping Paul



 
 
Thread Tools Display Modes
  #1  
Old June 6th 19, 07:53 PM posted to alt.comp.hardware.pc-homebuilt
Shadow[_2_]
external usenet poster
 
Posts: 174
Default Ping Paul

Thank you for the code. It compiled fine under an old bcc32.exe I had
hanging around and also GCC under my current Devuan Linux.

58.880 KRDRec.exe
5.600 KRDRec.Linux (after a strip)
160.261 report_.klr.enc1
161.023 report_.klr.txt
161.023 report_.klrLinux.txt

Both txt files were identical. Note the Linux executable was
1/10th the size of Borland's. Still, both tiny, no errors - perfect.
I'll be keeping the Linux version handy to use within the
bootdisk as ./KRDRec.Linux. Then I can grep and "grope" through the
txt to my heart's content.

[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012
  #2  
Old June 7th 19, 03:41 AM posted to alt.comp.hardware.pc-homebuilt
Paul[_26_]
external usenet poster
 
Posts: 1,009
Default Ping Paul

Shadow wrote:
Thank you for the code. It compiled fine under an old bcc32.exe I had
hanging around and also GCC under my current Devuan Linux.

58.880 KRDRec.exe
5.600 KRDRec.Linux (after a strip)
160.261 report_.klr.enc1
161.023 report_.klr.txt
161.023 report_.klrLinux.txt

Both txt files were identical. Note the Linux executable was
1/10th the size of Borland's. Still, both tiny, no errors - perfect.
I'll be keeping the Linux version handy to use within the
bootdisk as ./KRDRec.Linux. Then I can grep and "grope" through the
txt to my heart's content.

[]'s


You might still have to adjust the code for line
endings, depending on your preference. What I did
at the end of the code, is convert from Linux line
endings from the KAV output, to Windows line endings.
A Linux text editor can certainly accept Windows line
endings, so you don't absolutely have to fix it. I
didn't put any conditional code in there to suit the
situation, just enough code so it wouldn't be a
nuisance under normal circumstances.

There are even a few Sysinternals utilities that get
the line endings wrong, which is something that doesn't
make a lot of sense.

In any case, I'm glad the other poster figured out
the encoding, something I'm not good at.

Paul
  #3  
Old June 8th 19, 11:35 PM posted to alt.comp.hardware.pc-homebuilt
Shadow[_2_]
external usenet poster
 
Posts: 174
Default Ping Paul

On Thu, 06 Jun 2019 22:41:05 -0400, Paul
wrote:

Shadow wrote:
Thank you for the code. It compiled fine under an old bcc32.exe I had
hanging around and also GCC under my current Devuan Linux.

58.880 KRDRec.exe
5.600 KRDRec.Linux (after a strip)
160.261 report_.klr.enc1
161.023 report_.klr.txt
161.023 report_.klrLinux.txt

Both txt files were identical. Note the Linux executable was
1/10th the size of Borland's. Still, both tiny, no errors - perfect.
I'll be keeping the Linux version handy to use within the
bootdisk as ./KRDRec.Linux. Then I can grep and "grope" through the
txt to my heart's content.

[]'s


You might still have to adjust the code for line
endings, depending on your preference. What I did
at the end of the code, is convert from Linux line
endings from the KAV output, to Windows line endings.
A Linux text editor can certainly accept Windows line
endings, so you don't absolutely have to fix it. I
didn't put any conditional code in there to suit the
situation, just enough code so it wouldn't be a
nuisance under normal circumstances.


Output is identical (text wise) under both OS. EOL not a
problem. Didn't try grep, haven't run another scan yet. Might need
dos2unix to fix it.

There are even a few Sysinternals utilities that get
the line endings wrong, which is something that doesn't
make a lot of sense.


Most text editors (except maybe notepad) automatically (or ask
if you want it to) convert to DOS/Windows format.

In any case, I'm glad the other poster figured out
the encoding, something I'm not good at.


I USED to be. That's what's giving me anxiety attacks. Or
maybe it's just Bolsonaro's speeches. Ugh.

[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Ping Paul Buffalo Asus Motherboards 5 November 1st 12 05:09 PM
Ping: Paul Buffalo Nvidia Videocards 13 July 22nd 12 11:31 PM
Ping: Paul sdlomi2 Homebuilt PC's 3 April 28th 08 01:42 AM
PING: paul sdlomi2[_2_] Asus Motherboards 2 October 3rd 07 11:22 AM
PING: Paul Paul Asus Motherboards 0 October 13th 04 11:51 PM


All times are GMT +1. The time now is 11:47 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Copyright 2004-2019 ComputerBanter.com.
The comments are property of their posters.