- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I know this is not a Fortran problem but may be related to.
I have been using Adam Solesby's CustomCommentOut macro for a long time in two PCs (W98SE, cvf 6.6b). I have made some mods to the macro, striping what conserns to /*xxx*/ type of comment, and using ActiveDocument.language = dsFortran_Free and ActiveDocument.language = dsFortran_Fixed to chose the type of comment to be used.
I recently updated to XP SP2 in both PCs, reintalled CVF, and in one of then dsFortran_Free and dsFortran_Fixed return with no value. In the other PC the same macro works ok. I made a mod using the sample.dsm Function FileType to get .for or f90. That worked for the type of comment to be used but other objects/commands fail. I have no experience on the VB script language and after many tries have given up finding what makes the macro fail in just that PC.
I cheked Developer Studio settings on both PCs and they 'seem' to be the same (PCs are in diferent cities and I may have missed something).
I tried also to reinstall (without uninstalling) CVF but the problem persists.
The 'good' PC is an Athlon XP 2400,512Mb,Asus A7N266.
The 'bad' PC is a Semprom 1300,512M,Asus A7S266.
The XP used in the 'bad' one is the same I had installed in a now desactivated PC. In the desactivated PC (AMD K6II 450, 128M) the macro worked ok, so the problem does not seems the XP itself (media, version,...).
I would apreciate some help.
Thanks
Geraldo
I know this is not a Fortran problem but may be related to.
I have been using Adam Solesby's CustomCommentOut macro for a long time in two PCs (W98SE, cvf 6.6b). I have made some mods to the macro, striping what conserns to /*xxx*/ type of comment, and using ActiveDocument.language = dsFortran_Free and ActiveDocument.language = dsFortran_Fixed to chose the type of comment to be used.
I recently updated to XP SP2 in both PCs, reintalled CVF, and in one of then dsFortran_Free and dsFortran_Fixed return with no value. In the other PC the same macro works ok. I made a mod using the sample.dsm Function FileType to get .for or f90. That worked for the type of comment to be used but other objects/commands fail. I have no experience on the VB script language and after many tries have given up finding what makes the macro fail in just that PC.
I cheked Developer Studio settings on both PCs and they 'seem' to be the same (PCs are in diferent cities and I may have missed something).
I tried also to reinstall (without uninstalling) CVF but the problem persists.
The 'good' PC is an Athlon XP 2400,512Mb,Asus A7N266.
The 'bad' PC is a Semprom 1300,512M,Asus A7S266.
The XP used in the 'bad' one is the same I had installed in a now desactivated PC. In the desactivated PC (AMD K6II 450, 128M) the macro worked ok, so the problem does not seems the XP itself (media, version,...).
I would apreciate some help.
Thanks
Geraldo
Link Copied
0 Replies

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page