Eryck Abecassis

since few days, with a max patch, this error message is 

I check that line~ is correctly in the Externals

and when I create a line~, there is no problem

(of course I tried to delete max window and restart

the patch, but the same persisting error appears

there is no pain, but I would like to understand

since few days, with a max patch, this error message is 
appearing in Max window
error: line~ not such object
I check that line~ is correctly in the Externals
(he is)
and when I create a line~, there is no problem

(of course I tried to delete max window and restart
the patch, but the same persisting error appears

not-justified-error

>since few days, with a max patch, this error message is

>I check that line~ is correctly in the Externals

>and when I create a line~, there is no problem

>(of course I tried to delete max window and restart

>the patch, but the same persisting error appears

>there is no pain, but I would like to understand

>Hello
>
>since few days, with a max patch, this error message is
>appearing in Max window
>error: line~ not such object
>I check that line~ is correctly in the Externals
>(he is)
>and when I create a line~, there is no problem
>
>(of course I tried to delete max window and restart
>the patch, but the same persisting error appears
>
>there is no pain, but I would like to understand
>

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

(of course there is two, one in the main max folder

and one in the library >application support>cycling 74 plugin support)

nothing forbidden !!? anyway I tried a trashing of this library files, but no way

I trashed the prefs
I checked for an other line~ 
(of course there is two, one in the main max folder
and one in the library >application support>cycling 74 plugin support)
nothing forbidden !!? anyway I tried a trashing  of this library files, but no way

>(of course there is two, one in the main max folder

>and one in the library >application support>cycling 74 plugin support)

>nothing forbidden !!? anyway I tried a trashing of this library 

>I trashed the prefs
>I checked for an other line~
>(of course there is two, one in the main max folder
>and one in the library >application support>cycling 74 plugin support)
>nothing forbidden !!? anyway I tried a trashing  of this library 
>files, but no way

Windows stop code errors alert the user to an error. While some stop codes require a specific fix (check out the above list of Windows stop code error fixes), there are a few basic Windows troubleshooting tricks you can try.

The first fix is the easiest and most obvious: restarting your computer. Restarting your computer fixes a huge amount of issues, and there is a reason "switching it off and on again" is a running joke (but the first go-to fix) in the IT world.

SFC and CHKDSK are Windows system utilities you can use to fix a corrupt file system. At times, Windows files become corrupt and cause errors across your system. These tools scan your system and repair the broken files along the way.

Before running the SFC command, you need to check it is working properly. To do this, we use the Deployment Image Servicing and Management tool, or DISM. Like SFC, DISM is an integrated Windows utility with a wide range of functions. In this case, the DISM Restorehealth command ensures that our next fix will work properly.

Type Command Prompt (Admin) in the Start menu search bar, then right-click and select Run as administrator to open an elevated Command Prompt.

Type the following command and press Enter: DISM /online /cleanup-image /restorehealth

Wait for the command to complete. The process can take up to 20 minutes, depending on your system's health. The process seems stuck at certain times, but wait for it to complete.

When the process completes, type sfc /scannow and press Enter.

Next up, run CHKDSK. Unlike SFC, CHKDSK scans your entire drive for errors, whereas SFC scans Windows files specifically. Like SFC, run the CHKDSK scan from the Command Prompt to fix your machine.

Type command prompt in your Start menu search bar, then right-click the best match and select Run as administrator. (Alternatively, press Windows key + X, then select Command Prompt (Admin)from the menu.)

Next, type chkdsk /r and press Enter. The command will scan your system for errors and fix any issues along the way.

After SFC and CHKDSK complete, fixing any corrupt files along the way, restart your system. Then, attempt to access the restricted files.


The first fix is the easiest and most obvious: restarting your computer. Restarting your computer fixes a huge amount of issues, and there is a reason "switching it off and on again" is a running joke (but the first go-to fix) in the IT world.

2. Run SFC and CHKDSK

SFC and CHKDSK are Windows system utilities you can use to fix a corrupt file system. At times, Windows files become corrupt and cause errors across your system. These tools scan your system and repair the broken files along the way.

Type Command Prompt (Admin) in the Start menu search bar, then right-click and select Run as administrator to open an elevated Command Prompt.
Type the following command and press Enter: DISM /online /cleanup-image /restorehealth
Wait for the command to complete. The process can take up to 20 minutes, depending on your system's health. The process seems stuck at certain times, but wait for it to complete.
When the process completes, type sfc /scannow and press Enter.
windows 10 dism sfc scannow
Next up, run CHKDSK. Unlike SFC, CHKDSK scans your entire drive for errors, whereas SFC scans Windows files specifically. Like SFC, run the CHKDSK scan from the Command Prompt to fix your machine.

Type command prompt in your Start menu search bar, then right-click the best match and select Run as administrator. (Alternatively, press Windows key + X, then select Command Prompt (Admin)from the menu.)
Next, type chkdsk /r and press Enter. The command will scan your system for errors and fix any issues along the way.
After SFC and CHKDSK complete, fixing any corrupt files along the way, restart your system. Then, attempt to access the restricted files.

not justified error ?