Hey Keltio, could you add some coverting utilts to the edit or format -> convert menu:
1) OEM -> ANSII
2) ANSII -> OEM
I opened a file today with RadASM and it was one long single line of text.... I had to convert it with another utility before I could continue with RadASM...
:NaN:
1) OEM -> ANSII
2) ANSII -> OEM
I opened a file today with RadASM and it was one long single line of text.... I had to convert it with another utility before I could continue with RadASM...
:NaN:
Hi NaN,
"One long single line of text" - that means the lines were terminated by LF only (0Ah) not CRLF.
I do not think it has anything to do with OEM<->ANSI conversion, I'd rather say it's UNIX<->DOS conversion.
Anyway, it would be a good idea if RadASM broke lines on any (LF, CRLF, CR) line terminator.
"One long single line of text" - that means the lines were terminated by LF only (0Ah) not CRLF.
I do not think it has anything to do with OEM<->ANSI conversion, I'd rather say it's UNIX<->DOS conversion.
Anyway, it would be a good idea if RadASM broke lines on any (LF, CRLF, CR) line terminator.
There's more to say. RadASM would crash on files with lines terminated by LF only.
Try to replace CRLF in ReBar.Asm with a LF only. Then open ReBar.rap in RadASM. Boom!
WinNT4 SP6a, RadASM 2.0.3.2
Try to replace CRLF in ReBar.Asm with a LF only. Then open ReBar.rap in RadASM. Boom!
WinNT4 SP6a, RadASM 2.0.3.2
hi all,
if possible I would like support for special characters in find/replace
eg.
^t = tab
^p = CRLF
similar to that well know text/hex editor!
thanks!
if possible I would like support for special characters in find/replace
eg.
^t = tab
^p = CRLF
similar to that well know text/hex editor!
thanks!
:alright: What about the full default Regular Expression notation:
Posted on 2003-08-28 10:11:13 by pelaillo
Posted on 2003-08-28 10:11:13 by pelaillo
This version of RAEdit.dll should take care of the CR+LF problem.
KetilO
KetilO
Hi X05 & pelaillo
Implementing the full default Regular Expression notation is a lot of work.
I will see if I can find the time.
KetilO
Implementing the full default Regular Expression notation is a lot of work.
I will see if I can find the time.
KetilO
This version of RAEdit.dll should take care of the CR+LF problem.
In my case - it did not. RadASM still crashes on ReBar.Asm with LF.
The error is
tooltip_class32: radasm.EXE - Application error
Instruction at "0x00430044" tried to access memory at 0x00000000. Memory cannot be "written"
(or something like that - I have Polish message)
Hi Morris
Could you upload the file that causes RadASM to GPF.
KetilO
Could you upload the file that causes RadASM to GPF.
KetilO
As I said before, the file is ReBar.Asm ($RadASM$\Masm\Projects\ReBar from official RadASM package).
All I did was:
1. opened ReBar.Asm in FAR editor and saved with LF as the line terminator
2. opened ReBar.rap in RadASM -> Boom!
ReBar.Asm is dated 2003-08-18 15:23
I just checked and if the file is terminated with CR only, it is okay (no crash)
All I did was:
1. opened ReBar.Asm in FAR editor and saved with LF as the line terminator
2. opened ReBar.rap in RadASM -> Boom!
ReBar.Asm is dated 2003-08-18 15:23
I just checked and if the file is terminated with CR only, it is okay (no crash)
Hmmm, I tried this at home on Win98, and RadASM does not crash on the LF-terminated ReBar.Asm... I have to check it on other WinNT4 machines.
I just checked it on Win2K PRO SP3 and I got:
RadASM - ReBar: RadASM.exe - Application error
Instruction at "0x00570068" tried to access memory at address "0x00000001". Memory cannot be "written".
I just checked it on Win2K PRO SP3 and I got:
RadASM - ReBar: RadASM.exe - Application error
Instruction at "0x00570068" tried to access memory at address "0x00000001". Memory cannot be "written".